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

changeify

v0.1.2

Published

Create a change log for an npm project based on structured commit messages

Downloads

4

Readme

changeify

Create a change log for an npm project based on structured commit messages.

How it works

Tag all your commit messages with either breaking, add, fix or doc and then before a release run changeify. Changeify will:

  1. Generate a changelog separated into the different sections
  2. Commit the changelog
  3. Bump the version based on the type of changes made since the last release (optional)
  4. Publish to npm (optional)
  5. Push to origin (optional)

Example commit message:

Change signature of function foo

[breaking]

The argument order was swithed because the new one is superior...

The tag "[breaking]" is case insensitive and can be placed anywhere in the commit message except for the header. The header is what will be included in the changelog. Look at the changelog of this project for an example.

All commits without any tags will be ignored when generating the change log and determening the new version.

Usage

Either the module globally and use it in any project or locally and add it as an npm script.

Run changeify -n for a dry run which will print the changelog and the next version to the console.

Run changeify to perform steps 1 and 2 mentioned above. Add flag -p --publish to also perform steps 3-5.