3 ms·
We have a very similar setup (except s/Next.js/Remix) and went with npm workspaces + Task [1], and it's working really, really well so far. This is our second i
by elliotbnvl 2y ago
We have a very similar setup (except s/Next.js/Remix) and went with npm workspaces + Task [1], and it's working really, really well so far. This is our second iteration of a monorepo (first one was a straight React SPA bundled with Vite instead of Remix).
We have a root Taskfile that references our JS and Go taskfiles and wraps / abstracts all tasks. It's good for dependency management and task orchestration (`task lint` will run lint in both JS and Go for example, and `task test` does the same).
TypeScript sharing between packages can be a lil' funky, but so far it's super solid. Happy to share more if it would be helpful.
The nice thing is that this just relies on npm, which means setup is simple and straightforward, and we benefit from all of the stability and continual improvements npm brings to the table.
[1]: https://taskfile.dev/ https://taskfile.dev/