- yarn classic workspaces already do what we need
- The main benefit of turbo, the cache, is already disabled on dev builds. On
production builds, turbo doesn't support `next build` (this is mentioned in
Vercel's docs).
- We're not using their remote cache
- Maybe there is a monorepo size when the yarn workspace approach gets
unwieldly, but I feel we're not near that point.
Will bring it back if it gets missed.
VSCode still gives an error
We had to set the type to module to get the `import` to work. Setting .mjs
didn't work (eslint didn't recognize the file). Setting the type to module
should be (based on my current understanding) not affect us negatively since we
are exporting a TypeScript library not a bundled one, and all the other source
files apart from this are intended to be `*.ts`.
Refs:
- https://jeremyrichardson.dev/blog/saga_of_learning_exports_property_in_packagejson
- https://github.com/eslint/eslint/discussions/17021