a023b6456c
* Fix design/monorepo.md DO blog link [skip ci] * Fix README signup wording [skip ci] * Update README link [skip ci] * Fix CONTRIBUTING signup wording [skip ci] * Fix CONTRIBUTING Slack link [skip ci]
2.3 KiB
2.3 KiB
Why is Babel a monorepo?
The tool for managing the monorepo in Babel has been extracted out as Lerna
Juggling a multimodule project over multiple repos is like trying to teach a newborn baby how to ride a bike.
Babel follows a monorepo approach, all officially maintained modules are in the same repo.
This is quite taboo but let's look at the pros and cons:
Pros:
- Single lint, build, test and release process.
- Easy to coordinate changes across modules.
- Single place to report issues.
- Easier to setup a development environment.
- Tests across modules are run together which finds bugs that touch multiple modules more easily.
Cons:
- Codebase looks more intimidating.
- Repo is bigger in size.
- Can't
npm installmodules directly from GitHub - ???
This is dumb! Nobody in open source does this!
React, Meteor, and Ember, among others, do this.