mirror of
https://github.com/hanzoai/babel.git
synced 2026-09-24 16:56:45 +00:00
Yarden ShohamandGitHub
74db7925c3
[skip ci] Use updated native GitHub markdown `Note` admonition - Follows https://github.com/babel/babel/pull/15443 GitHub will render it with an icon and color the blockquote. The docs: https://docs.github.com/en/get-started/writing-on-github/getting-started-with-writing-and-formatting-on-github/basic-writing-and-formatting-syntax#alerts Signed-off-by: Yarden Shoham <[email protected]>
2.4 KiB
2.4 KiB
Why is Babel a monorepo?
Note
We don't use
lernato manage packages inside the monorepo, but yarn workspaces with an additional custom plugin.
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.