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

changelog-publish

v1.1.0

Published

Move unreleased changes from CHANGELOG.md into a new release

Downloads

3

Readme

changelog-publish

A tiny CLI tool for adding a version to unreleased changes in your changelog when you bump the package version on your Node.js project.

Usage

This tool assumes you're keeping a changelog with a 2nd-level header called "Unreleased" for unreleased changes, as per the keep a changelog spec.

1: Install it

Install the tool in your project:

npm install changelog-publish

2: Add a version script

In your package.json add a version entry under scripts:

{
  "scripts": {
    "version": "changelog-publish <your github URL> && git add CHANGELOG.md"
  }
}

Now, when you run npm version <patch|minor|major|whatever>, any changes in the Unreleased section will be moved into a section for your new package version.

The git add part is to make sure the changes to your changelog get included in the same commit as your version-bump.

That's it! That's all this tool does! Ta-da!