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

changesets-toolkit

v0.1.0

Published

toolkit for changesets which make commit message more automatic and changelogs more readable

Downloads

169

Readme

changesets-toolkit

中文 README

This package supplies CommonJS commit/changelog hooks and release wrappers for Changesets 3.

Requirements

  • Node.js ^22.11 || ^24 || >=26
  • pnpm >=11
  • @changesets/cli@^3.0.0 installed by the consuming project

Configuration

Configure .changeset/config.json:

{
  "changelog": ["changesets-toolkit/dist/changelog.js", {}],
  "commit": ["changesets-toolkit/dist/commit.js", {}],
  "updateInternalDependencies": "patch"
}

Set CHANGESET_READ_REPO_TOKEN to a GitHub token with repository read access if changelog entries should use GitHub usernames. Without it, the commit email is used.

Commit and changelog hooks

changeset add creates a commit message such as:

chore(changeset): 🦋 @package-name:patch

changeset version writes changelog entries such as:

- feat: this is a test @author · 2025-01-01 · [#abc1234](https://github.com/owner/repo/commit/abc1234)

changeset_version

changeset_version [--beta] [--filter <glob>] [--git-push | --no-git-push]
  • The first --beta run enters the beta prerelease mode. Later runs continue that prerelease and keep .changeset/pre.json plus .changeset/pre/.
  • A stable run automatically exits an active prerelease before versioning.
  • --filter matches package names but applies to the whole changeset file. A changeset that releases multiple packages is never split. Hidden changesets are restored after success or failure, and leftovers from an interrupted run are recovered at startup.
  • Git push is disabled by default. --git-push pushes the current branch and reports detached-head, missing-target, or push errors. --no-git-push is an explicit no-push form.
  • Changesets 3 exit code 1 is preserved when there are no unreleased changesets.

changeset_publish

changeset_publish [--no-git-tag]

The default command publishes, creates tags, and pushes them. --no-git-tag forwards the option to Changesets and skips tag pushing. CI runs this wrapper through changesets/action/publish@v2, so tags point at the generated version commit while the action still creates GitHub Releases. The wrapper also remains available for local/manual publishing.