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

@cto.af/monopub

v0.1.2

Published

This project is a relatively-simplified approach to publishing multiple NPM packages from a monorepo. It handles these use cases:

Downloads

433

Readme

@cto.af/monopub

This project is a relatively-simplified approach to publishing multiple NPM packages from a monorepo. It handles these use cases:

  • Setting the version number of all sub-packages to the same version as the root project. This is usually performed during the run of npm version by setting the version script to monopub version. This will modify each of the sub-project package.json files and add them to the pending git commit that npm version creates.
  • Deleting unwanted keys from all package.json files. Some projects like to remove the devDependencies, scripts, and other development-focused information from the package.json file before publishing. This would be run during the GitHub Actions script that is publishing the package to npm with monopub delete devDependencies,scripts.
  • Executing a script on all of the sub-pacakges. This is used during the GitHub Actions script that is publishing the package to npm with monopub exec 'npm publish'.
  • By default, private packages are ignored. Include them with --private.
  • All actions are run in dependency order, so that a sub-project that depends on another sub-project is evaluated after its dependency.

Installation

npm install @cto.af/monopub

CLI

Usage: monopub [options] [command]

Options:
  --cwd <directory>      Operate from given directory (default: cwd)
  -h, --help             display help for command
  -p, --packages <glob>  Glob to find names of sub-package directories.  Can be
                         specified multiple times. (default: [])
  -P, --private          Include private packages
  -V, --version          output the version number

Commands:
  delete <fields>        Delete this set of comma-separated fields from all
                         package files.
  exec <command>         Run the given command in a shell for each package
                         file.
  help [command]         display help for command
  order                  Output the order in which packages will be processed.
  version                Update version of all sub-repos to match the root.
                         Should be called from the npm "version" script.

delete

Usage: monopub delete [options] <fields>

Delete this set of comma-separated fields from all package files.

Options:
  -h, --help             display help for command

Global Options:
  --cwd <directory>      Operate from given directory (default: cwd)
  -p, --packages <glob>  Glob to find names of sub-package directories.  Can be
                         specified multiple times. (default: [])
  -P, --private          Include private packages
  -V, --version          output the version number

exec

Usage: monopub exec [options] <command>

Run the given command in a shell for each package file.

Options:
  -h, --help             display help for command

Global Options:
  --cwd <directory>      Operate from given directory (default: cwd)
  -p, --packages <glob>  Glob to find names of sub-package directories.  Can be
                         specified multiple times. (default: [])
  -P, --private          Include private packages
  -V, --version          output the version number

order

Usage: monopub order [options]

Output the order in which packages will be processed.

Options:
  -h, --help             display help for command

Global Options:
  --cwd <directory>      Operate from given directory (default: cwd)
  -p, --packages <glob>  Glob to find names of sub-package directories.  Can be
                         specified multiple times. (default: [])
  -P, --private          Include private packages
  -V, --version          output the version number

version

Usage: monopub version [options]

Update version of all sub-repos to match the root.  Should be called from the
npm "version" script.

Options:
  -h, --help             display help for command

Global Options:
  --cwd <directory>      Operate from given directory (default: cwd)
  -p, --packages <glob>  Glob to find names of sub-package directories.  Can be
                         specified multiple times. (default: [])
  -P, --private          Include private packages
  -V, --version          output the version number

API

Full API documentation is available.

Example:

import {MonoRoot} from './index.js';
const m = await new MonoRoot(opts).init();
m.delete(['devDependencies', 'scripts']);
m.setVersions();
await m.execAll({stdio: 'inherit'}, 'npm publish');
await m.save(true); // True to do git add for changed files

Tests codecov