npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

mondorepo

v0.1.705

Published

Management for collections of packages across teams

Downloads

7

Readme

mondorepo

Dependencies Status npm version MIT Licence

mondorepo

Management for collections of packages across teams

For the increasingly common scenario where teams need to work on more than one npm package at a time, mondorepo enables collaboration on a collection of jointly developed repositories that may contain one or multiple projects themselves.

One project, multiple packages and repositories, all aware of each other at runtime.

Motivation

The Node.js package ecosystem has been traditionally developed following the one package per repository rule, which is a workable solution for developing packages that are small in size or complexity and live in relative isolation.

As projects' scale increases this approach has a couple significant problems.

  1. The amount of code in a complex project often increases beyond what would ideally live in a single package.
  2. Most times, multiple teams of developers need to collaborate on concurrently developed packages managed in separate repositories.

Traditional approaches to solve these problems are:

  1. Use relative paths across a huge codebase
  2. Include jointly developed packages inside the main project's node_modules directory.
  3. Following the monorepo approach (mono not mondo).

While there are potential advantages to each of these approaches, here at Sencha we decided to tackle the problem in a way that projects remain modular and sub packages can be developed on their own.

We call these mondorepos.

mondorepos ("mondo: large, big")

As an alternative to monolithic repositories, mondorepo enables teams to collaborate on big complex projects that span across multiple repositories. Each subpackage can be a mondorepo on its own and so on.

An example of this project structure would look like this:

Repository: 'awesomecorp/MyAwesomeProject'
MyAwesomeProject/
    index.js
    package.json      // <- contains a reference to "awesomecorp/My-pkg" under "mondo.uses.My-pkg"

Repository: 'awesomecorp/My-pkg'
MyAwesomeProject/
    index.js
    package.json
    

Running mondo install will connect all used repositories (declared inside mondo.uses) and make My-pkg available to be used on a simple require('My-pkg') statement, isn't that neat?

This effectively means that each subpackage can be developed on its own if needed, but also can be included as part of any other project that wants to jointly develop a bunch of its own requirements.

Getting started

Install mondorepo globally

We prefer yarn but npm is also fine:

$ yarn global add mondorepo

Bring all other repositories used by your project into play

Once you checked out a project that uses mondorepo, just run:

$ mondo install

If you have a set of known forks configured and wish to use them when installing the project, run:

$ mondo install --forks

Getting help

For help on how to use the CLI tool run:

$ mondo help

For help configuring your project as a mondorepo, check our Getting started guide.

Contributing

Please read CONTRIBUTING.md for details on the code of conduct, and the process for submitting pull requests.

Versioning

mondorepo uses SemVer for versioning. For the versions available, see the tags on this repository.

License

This project is licensed under the MIT License - see the LICENSE file for details