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

update-workspace-root-version

v1.0.1

Published

Update the workspace root version in a monorepo

Downloads

100

Readme

This project uses GitHub Actions for continuous integration.

update-workspace-root-version

  1. Why use it?
  2. Usage
  3. Compatibility
  4. Contributing
  5. License

Why use it?

Git tags mark a specific point in a repo's history and are usually created at the time of release. Thanks to these tags, we can easily send people links and point to specific code. We can also compare tags to see how files have changed.

Creating tags can be tricky in monorepos, because we can release many packages at once. How do we create just 1 tag (no matter how many packages) and give it a name that resembles a semantic version?

Solution: We let the version of the workspace root indicate the state of the whole project, then set the tag name to be this version. update-workspace-root-version helps you update the version automatically.

Usage

At the workspace root, install update-workspace-root-version as a development dependency.

Then, run the codemod before you create a tag. For example, after changesets updates all package versions, we update the workspace root's version.

/* package.json */
{
  "scripts": {
    "release:changelog": "changeset version; update-workspace-root-version",
  },
  "devDependencies": {
    "@changesets/cli": "...",
    "update-workspace-root-version": "..."
  }
}

Arguments

# Highest version (default)
update-workspace-root-version --algorithm highest-version

# Increment by one
update-workspace-root-version --algorithm increment-by-one

Limitations

The codemod assumes that every package follows semantic versioning. It is designed to cover typical cases.

Compatibility

  • Node.js v18 or above

Contributing

See the Contributing guide for details.

License

This project is licensed under the MIT License.