melos

<p align="center">
  <a href="https://melos.invertase.dev/~melos-latest">
  <img src="https://static.invertase.io/assets/melos-logo.png" alt="Melos" /> <br /><br />
  </a>
  <span>A tool for managing Dart and Flutter projects, with one or many packages, inspired by <a href="https://lerna.js.org">Lerna</a>.</span>
</p>

<p align="center">
  <a href="https://github.com/invertase/melos#using-melos"><img src="https://img.shields.io/badge/maintained%20with-melos-f700ff.svg?style=flat-square" alt="Melos" /></a>
  <a href="https://docs.page"><img src="https://img.shields.io/badge/powered%20by-docs.page-34C4AC.svg?style=flat-square" alt="docs.page" /></a>
 <a href="https://invertase.link/discord">
   <img src="https://img.shields.io/discord/295953187817521152.svg?style=flat-square&colorA=7289da&label=Chat%20on%20Discord" alt="Chat on Discord">
 </a>
</p>

<p align="center">
  <a href="https://melos.invertase.dev/~melos-latest">Documentation</a> &bull;
  <a href="https://github.com/invertase/melos/blob/main/LICENSE">License</a>
</p>

---

## About

Splitting up large code bases into separate independently versioned packages is
extremely useful for code sharing. However, making changes across many
repositories is _messy_ and difficult to track, and testing across repositories
gets complicated really fast.

To solve these (and many other) problems, some projects will organize their code
bases into multi-package repositories (sometimes called
[monorepos](https://en.wikipedia.org/wiki/Monorepo))

**Melos is a tool that optimizes the workflow around managing multi-package
repositories with git and Pub.**

It is in active development and is in use on projects such as
[FlutterFire](https://github.com/firebase/flutterfire) and
[Flame](https://github.com/flame-engine/flame), see
[Projects using Melos](https://melos.invertase.dev/~melos-latest#projects-using-melos)
for more projects.

Melos is for applications just as much as it is for packages that are published
to [pub.dev](https://pub.dev). A workspace can contain your Flutter and Dart
applications together with the internal packages that they share, and Melos
will run your scripts, tests and analysis across all of them, generate IDE run
configurations for the applications and version them, including the build
number of a version like `1.2.3+45`. Nothing has to be published to use Melos.

Melos is not limited to monorepos either. It works just as well in a repository
with a single application or package, where you can still use features like
versioning, changelog generation, publishing and scripts, see
[Using Melos without a monorepo](#using-melos-without-a-monorepo).

### How does Melos relate to other monorepo tools?

Melos is the monorepo tool for the Dart and Flutter ecosystem. If you are coming
from another ecosystem, Melos is the Dart and Flutter alternative to tools like:

- [Lerna](https://lerna.js.org), [Nx](https://nx.dev),
  [Turborepo](https://turborepo.com) and [Rush](https://rushjs.io) for
  JavaSc