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

@repo-toolkit/changelog

v0.6.0

Published

Shared conventional changelog preset, generator, and CLI for repository releases

Readme

@repo-toolkit/changelog

Shared conventional changelog preset, generator, and CLI for repository releases.

Installation

pnpm add -D @repo-toolkit/changelog

Config File

Use --config when you want repo-specific options such as custom commit types, scope filtering, ignored commits, or custom issue and commit URLs.

/** @type {import('@repo-toolkit/changelog').ChangelogConfig} */
export default {
  ignoreCommits: /^chore: release candidate /,
  issuePrefixes: ['#', 'WEB-'],
  scope: ['api', 'ui'],
  scopeOnly: true,
  types: [
    { type: 'feat', section: 'Features' },
    { type: 'fix', section: 'Bug Fixes' },
    { type: 'build', section: 'Build' },
    { type: 'docs', section: 'Docs' },
    { type: 'chore', effect: 'hidden' },
  ],
};

Run it with:

repo-toolkit-changelog --config changelog.config.mjs

CLI flags override values from the config file.

Use a JavaScript config file when you need RegExp values such as ignoreCommits or formatter callbacks such as formatIssueUrl. JSON config files only work for plain data options.

CLI

repo-toolkit-changelog

Useful flags:

  • --config <path>
  • --cwd <path>
  • --output <path>
  • --tag-prefix <prefix>
  • --release-count <number>
  • --first-release
  • --no-skip-unstable
  • --no-output-unreleased

JavaScript API

import { generateChangelog } from '@repo-toolkit/changelog';

await generateChangelog({
  outputFile: 'CHANGELOG.md',
  tagPrefix: 'v',
  issuePrefixes: ['#', 'WEB-'],
  scope: 'api',
});

Supported Preset Options

  • types
  • ignoreCommits
  • issuePrefixes
  • scope
  • scopeOnly
  • preMajor
  • formatIssueUrl
  • formatCommitUrl
  • formatCompareUrl
  • formatUserUrl

Default Sections

  • feat -> Features
  • fix -> Bug Fixes
  • revert -> Reverts
  • docs -> Documentation
  • refactor -> Code Refactoring
  • perf -> Performance Improvements
  • build -> Build System
  • e2e -> End-to-end Testing

Hidden by default:

  • fix(deps)
  • ci
  • chore
  • style
  • test
  • release

effect is the preferred field for commit-type visibility. hidden is still accepted for compatibility with older upstream versions.