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

changelogfmt

v2.2.0

Published

Formats the reference links of Keep a Changelog style files.

Downloads

15

Readme

changelogfmt npm version

Formats the reference links of Keep a Changelog style files.

Overview

When maintaining a changelog file in the Keep a Changelog format, you need to manually add links to compare each version with the previous one.

You might also reference issues and pull requests, and unlike in GitHub comments, you need to explicitly add the Markdown link for those in your changelog.

This can be a bit cumbersome and error-prone. To ease that, let me introduce changelogfmt.

This tool takes your changelog as stdin, makes sure that each version has the proper GitHub compare URL (or adds it otherwise), identifies all # links to add the issue or PR link reference for all the missing ones, and outputs the new version to stdout.

Installation

npm install -g changelogfmt

Usage

Format given file, stdin or CHANGELOG.md otherwise, and print it to stdout:

changelogfmt whatever.md
changelogfmt < whatever.md
changelogfmt

Format given file or CHANGELOG.md otherwise, and overwrite it:

changelogfmt --write whatever.md
changelogfmt --write

My favorite way is from inside Vim, while editing the changelog file:

:%!changelogfmt

Development

# Lint the code.
npm run lint

Possible improvements

Pull requests are welcome!

  • Automatically fetch version dates from Git tags if missing (or validate existing ones too).
  • Add missing version entries based on Git tags.