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 🙏

© 2026 – Pkg Stats / Ryan Hefner

npm-scripts-conventional-changelog

v0.1.0

Published

Configuration for npm-scripts-config where conventional-changelog, commitlint and commitizen are ready to use.

Readme

npm-scripts-conventional-changelog

Configuration for npm-scripts-config where conventional-changelog, commitlint and commitizen are ready to use.

This configuration expose three commands:

  • commit: trigger commitizen to guide the developer to write a standardized commit message
  • commitmsg: used by husky to lint commit message when git commit is run
  • version: generates a changelog and it to the commit
  • preview-changelog: adds unreleased commits to changelog to preview the output (warning: do not commit this generated changelog)

commitizen, commitlint and conventional-changelog are configured to follow angular conventions.

Installation

npm install --save-dev npm-scripts-config npm-scripts-conventional-changelog

Create a new file that will load the configuration from this package.

.scriptsrc

{
    "@extends": "npm-scripts-conventional-changelog"
}

In your project you still need to specify which rules you want to use for commitlint and commitizen, but packages will already be installed. To specify those rules you need to create update the package.json and create a commitlint.config.js files:

package.json

{
    [...]
    "scripts": {
        "commit": "npm-scripts-config commit",
        "commitmsg": "npm-scripts-config commitmsg",
        "version": "npm-scripts-config version",
        "preview-changelog": "npm-scripts-config preview-changelog"
    },
    "config": {
        "commitizen": {
            "path": "cz-conventional-changelog"
        }
    },
    [...]
}

commitlint.config.js

module.exports = {
  extends: ["@commitlint/config-conventional"]
}