babel/doc/design/monorepo.md
2015-09-01 05:08:03 +01:00

1.9 KiB

Why is Babel a monorepo?

Juggling a multimodule project over multiple repos is like X.

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 ran together which finds bugs that touch multiple modules easier.

Cons:

  • Codebase looks more intimidating.
  • Repo is bigger in size.
  • ???

This is dumb! Nobody in open source does this!

React and Ember, among others, do this.

Previous discussion