"If a worker wants to do his job well, he must first sharpen his tools." - Confucius, "The Analects of Confucius. Lu Linggong"
Front page > Programming > You probably don&#t need a monorepo

You probably don&#t need a monorepo

Published on 2024-11-08
Browse:402

You probably don

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.

  1. A lot of bookkeeping and administrative tasks just disappear.
  2. Three shaking removes unused code either way.
  3. 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.

Release Statement This article is reproduced at: https://dev.to/lebbe/you-probably-dont-need-a-monorepo-50oc?1 If there is any infringement, please contact [email protected] to delete it
Latest tutorial More>

Disclaimer: All resources provided are partly from the Internet. If there is any infringement of your copyright or other rights and interests, please explain the detailed reasons and provide proof of copyright or rights and interests and then send it to the email: [email protected] We will handle it for you as soon as possible.

Copyright© 2022 湘ICP备2022001581号-3