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

@rossmcewan/semantic-release-nx

v0.2.0

Published

Plugins for `semantic-release` allowing it to be used with an Nx monorepo.

Downloads

27

Readme

@rossmcewan/semantic-release-nx

Apply semantic-release's automatic publishing to an Nx monorepo.

Why

The default configuration of semantic-release assumes a one-to-one relationship between a GitHub repository and an npm package.

This library allows using semantic-release with a single GitHub repository containing many npm packages.

How

Instead of attributing all commits to a single package, commits are assigned to packages based on the files that a commit touched.

If a commit touched a file in or below a package's root, it will be considered for that package's next release. A single commit can belong to multiple packages and may trigger the release of multiple packages.

Additionally, if a commit touches a file of a package that is a dependency of the current package, then the commit will also be included.

In order to avoid version collisions, generated git tags are namespaced using the given package's name: <package-name>-<version>.

Install

Both semantic-release and @rossmcewan/semantic-release-nx must be accessible in each monorepo package.

npm install -D semantic-release @rossmcewan/semantic-release-nx

Usage

Run semantic-release in an individual monorepo package and apply @rossmcewan/semantic-release-nx via the extends option.

On the command line:

$ npm run semantic-release -e @rossmcewan/semantic-release-nx

Or in the release config:

{
  "extends": "@rossmcewan/semantic-release-nx"
}

NOTE: This library CAN'T be applied via the plugins option.

{
  "plugins": [
    "@rossmcewan/semantic-release-nx" // This WON'T work
  ]
}

With Yarn Workspaces

$ yarn workspaces run semantic-release -e @rossmcewan/semantic-release-nx

With pnpm

pnpm has built-in workspace functionality for monorepos. Similarly to the above, you can use pnpm to make release in all packages:

pnpm -r --workspace-concurrency=1 exec -- npx --no-install semantic-release -e @rossmcewan/semantic-release-nx

Thanks to how npx's package resolution works, if the repository root is in $PATH (typically true on CI), semantic-release and @rossmcewan/semantic-release-nx can be installed once in the repo root instead of in each individual package, likely saving both time and disk space.

Advanced

This library modifies the context object passed to semantic-release plugins in the following way to make them compatible with a monorepo.

| Step | Description | | ------------------ | ----------------------------------------------------------------------------------------------------- | | analyzeCommits | Filters context.commits to only include the given monorepo package's commits and any commmits that affects packages the current package depends on. | | generateNotes | Filters context.commits to only include the given monorepo package's commits.Modifies context.nextRelease.version to use the monorepo git tag format. The wrapped (default) generateNotes implementation uses this variable as the header for the release notes. Since all release notes end up in the same Github repository, using just the version as a header introduces ambiguity. |

tagFormat

Pre-configures the tagFormat option to use the monorepo git tag format.