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

npm-dist-tag-test

v1.0.1

Published

testing npm dist-tag for adding security features to old versions without overriding latest

Downloads

2

Readme

How to release an old version of an NPM module

Let's assume we are currently at version 1.0.0 and need to make a security release for 0.1.x branch, 0.1.1. Here's how to do this without overriding the latest tag on NPM, which is on by default when running npm publish. This makes the assumption that you have properly released via git tags, otherwise you'll have to find proper GitShas.

  1. Fetch all git tags and checkout a new branch from the v0.1.0 release/tag git checkout -b 0.1.x v0.1.0
  2. Create a new branch for the 0.1.x series git checkout -b 0.1.x and push to GitHub
  3. Checkout a new branch (named whatever you want) for the 0.1.x security fix git checkout -b security-fix
  4. Make your changes and push the branch to GitHub
  5. Make a pull request to the 0.1.x branch
  6. Once approved, merge those changes
  7. Checkout the 0.1.x branch on your local and update the package.json to 0.1.1, update the CHANGELOG, and push directly to the 0.1.x branch
  8. Create a new tag git tag -a v0.1.1 -m 'v0.1.1' and push that tag git push --tags
  9. Publish to NPM with with the --tag flag npm publish --tag previous - this will prevent the 0.1.1 release from being marked as latest and installing in new projects rather than the 1.0.x release. (The usage of previous is arbitrary, as long as you don't type latest this can be whatever string you want)