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

changelog-gen-cli

v1.1.0

Published

Generate CHANGELOG.md from git conventional commits — zero dependencies

Readme

changelog-gen-cli

Generate a CHANGELOG.md from git conventional commits — zero npm dependencies.

Install

npm install -g changelog-gen-cli

Usage

# Generate CHANGELOG.md in the current repo
changelog-gen

# Preview output without writing (dry run)
changelog-gen --dry-run

# Limit history since a tag or date
changelog-gen --since=v1.0.0
changelog-gen --since=2024-01-01

# Highlight breaking changes
changelog-gen --breaking

# Write to a custom file
changelog-gen --output=CHANGES.md

# Combine flags
changelog-gen --dry-run --since=v2.0.0 --breaking

Options

| Flag | Description | |---|---| | --since <tag\|date\|ref> | Start of history range. Default: last git tag (or all if no tags) | | --output <file> | Output file path. Default: CHANGELOG.md | | --dry-run | Print to stdout instead of writing file | | --breaking | Highlight commits with BREAKING CHANGE: footer or ! after type | | --help, -h | Show help | | --version, -v | Show version |

Output Format

Follows the Keep a Changelog format and groups commits by type:

  • BREAKING CHANGESfeat!:, fix!:, or BREAKING CHANGE: footer
  • Featuresfeat:
  • Bug Fixesfix:
  • Performance Improvementsperf:
  • Code Refactoringrefactor:
  • Documentationdocs:
  • Build Systembuild:
  • CI/CDci:
  • Teststest:
  • Choreschore:

If git tags exist, versioned sections are generated automatically. The [Unreleased] section covers commits since the latest tag.

Example Output

# Changelog

...

## [Unreleased] - 2025-06-01

### Features

- add dark mode support (`a1b2c3d`)
- new --json output flag (`e4f5g6h`)

### Bug Fixes

- fix crash on empty repo (`7i8j9k0`)

## [v1.2.0] - 2025-05-15

### BREAKING CHANGES

- remove legacy --format flag (`l1m2n3o`)

Exit Codes

| Code | Meaning | |---|---| | 0 | Success | | 1 | Not a git repository | | 2 | Unexpected error |

Requirements

  • Node.js >= 16
  • Git installed and accessible in PATH
  • Must be run from inside a git repository

License

MIT