Re:I Love Monorepos–Except When They Are Annoying
by turtleyacht on Sunday March 09, 2025 @08:16PM
(#43315402)
Some lessons from monorepos:
Node Version Manager (nvm) with .nvmrc helps local conformance to a specific version of Node.js.
It's a chore to figure out utils/ depends on a/ and b/, but it's a good thing to add to the docs.
`npm pack` with `file://` may be easier to reason about than linking.
After changing a common/ package, there's risk to having to merge one package, wait for it to publish, and then consume that new version in the next package(s). Serial PRs and the whole team is waiting.
Re:I Love Monorepos–Except When They Are Annoying
by theamk on Sunday March 09, 2025 @08:07PM
(#43315346)
Note: this is all about JS monorepos, and it looks like most complains are about kinds which "develop and publish multiple npm packages from a single git repository"
I am not a JS programmer, so all the monorepo complaints seem pretty alien to me. They don't really apply to C++/Python monorepos I am familiar with.
Node Version Manager (nvm) with .nvmrc helps local conformance to a specific version of Node.js.
It's a chore to figure out utils/ depends on a/ and b/, but it's a good thing to add to the docs.
`npm pack` with `file://` may be easier to reason about than linking.
After changing a common/ package, there's risk to having to merge one package, wait for it to publish, and then consume that new version in the next package(s). Serial PRs and the whole team is waiting.
I am not a JS programmer, so all the monorepo complaints seem pretty alien to me. They don't really apply to C++/Python monorepos I am familiar with.