Set-up shared schemas in the monorepo

[izzyconner]

[izzyconner]

I'm at my wit's end with trying to get the schemas to be properly included in the frontend and backend apps with our current NX configuration, without getting a module error. Here are a few of the things I've tried so far:

• Using the tsconfig paths variable in the frontend and backend files to create an alias @org/schemas for the shared schemas lib. Intellisense is happy with it, but when I actually run the program it gets mad and throws a ModuleError. My guess is maybe it has something to do with the way the dist folders are structured/being built?
• Using the tsconfig referenences settings: https://www.typescriptlang.org/docs/handbook/project-references.html, combined with actually building the library using a manual tsc -b command. Here's some referenced instructions: https://stackoverflow.com/questions/47729344/how-to-share-code-between-typescript-projects
• In my desperation, I tried using yarn workspaces because I wasn't thinking and forgot about npm. Expectedly, yarn got mad.
• Linking the library (I don't think I built it correctly for it to be a package though?) via npm link following these instructions: https://stackoverflow.com/questions/8088795/installing-a-local-module-using-npm. I should maybe try this again, but not sure if it would work when we actually build and deploy it. Other instructions to try: https://medium.com/@AidThompsin/how-to-npm-link-to-a-local-version-of-your-dependency-84e82126667a

Some more things to try:

• Redo the monorepo. I know it sucks, but our tsconfigs and package.jsons are all out of whack right now with NX. The tsconfig files should really all be inheriting from the main one (from what I can understand, at least), but without that, it's pretty hard to take advantage of the library capability NX has. There's a few options for re-setting up the monorepo.
  -- Do it manually: https://earthly.dev/blog/setup-typescript-monorepo/#:~:text=How%20to%20Build%20a%20TypeScript%20Monorepo%20With%20NPM,...%207%20Define%20a%20Global%20tsconfig.json%20File%20
  -- Do it via Lerna, which actually uses NX: https://lerna.js.org/docs/getting-started
  -- Do it again via NX
• Try the references again. Solution one from this post has a github repo linked, and seems to have very simple package.json and tsconfig files - maybe I did something wrong initially? https://blog.logrocket.com/make-sharing-typescript-code-types-quick-easy/ (and another potential post: https://wallis.dev/blog/typescript-project-references)

For now, if I still can't get it working, I think I'll move back to having schema folders in both the frontend and backend apps - at the very least, the schemas are consolidated and up-to-date now.