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

monorepo-release

v0.1.0

Published

Automate versioning and publishing of packages in a monorepo

Downloads

3

Readme

:sailboat: Monorepo Release

Node functions that automate the independent versioning and publishing of packages in a monorepo.

Requires commit messages in the following format:

<type>(<scope>): <subject>

<scope> should be the name of the package intended to be released. The commit message format follows the angular commit message guidelines.

Note: for <scope> don't include the @scope/ prefix of the package (only the package name).

Commit message example

feat(package-a): add stuff to package-a

Commit message CLI

A commit message CLI builder like cz-customisable can be included in your project to ensure commit messages are always formatted correctly.

Changelogs

Changelogs can be generated with something like auto-changelog by setting the changelog command run for each package

Install auto-changelog in project

yarn add --dev auto-changelog

packages/package-a/package.json

"scripts": {
  "changelog": "auto-changelog"
},
"auto-changelog": {
  "output": "CHANGELOG.md",
  "tagPattern": "@scope/package-a@"
}

scripts/release.js

const { getPackages, release } = require('monorepo-release');
const packages = getPackages();

const config = {
  changelog: true,
  changelogCmd: 'yarn changelog',
};

packages.forEach(release(config));

Run script locally or in CI

node scripts/release.js

Requires initial package git tags to exist before release can be used to automate publishing

@scope/[email protected]
@scope/[email protected]

Generate tags manually or run a function available in this package to generate initial tags across current packages

Create initial tags: scripst/createTags.js

const { createTag, getPackages } = require('monorepo-release');
const packages = getPackages();

packages.forEach(createTag());

Run script

node scripts/createTags.js

Release: scripts/release.js

const { getPackages, release } = require('monorepo-release');
const packages = getPackages();

const config = {
  dryRun: true,
};

packages.forEach(release(config));

Config options and defaults

Run script locally or in CI

node scripts/release.js