If you have several npm packages inside the same "monorepo", you and your users would probably be better off if this was one big coherent package instead.
- A lot of bookkeeping and administrative tasks just disappear.
- Three shaking removes unused code either way.
- Unhealthy dependencies between each package is impossible, because everything is just one single dependency.
Instead of "monorepo", consider a monolith instead. That is, one huge application. It solves the same "issues", but with a lot less administration between the teams sharing the components.
Top comments (1)
It would, of course, still be ONE repo. But its not a monorepo, because there are only one application within that repo.