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.0.4

Published

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

Readme

Overview

中文 README

Configuration

Configure in .changeset/config.json:

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

GitHub Token

To get the changeset committer's username, you need to configure a GitHub token in the CHANGESET_READ_REPO_TOKEN environment variable. If not configured, the changeset committer's email will be used by default.

How to get a token:

  1. Log in to GitHub, go to Settings -> Developer settings -> Personal access tokens -> Tokens (classic)
  2. Click the Generate new token button to generate a token
  3. Check the read repo permission
  4. Copy the token to the environment variable

Commit

When running npx changeset, a commit message will be automatically generated in the following format: chore(changeset): 🦋 @package-name:patch

Changelog

When running npx changeset version, the following steps are performed:

  1. Parse the file content under .changeset/config.json and write to changelog in a specific format:
- feat: this is test @xxx · 2025-xx-xx · [#xxx](https://xxx)
- feat: this is a test @xxx · 2025-xx-xx · [#xxx](https://xxx)
  1. When child packages are updated, the parent package's changelog will also be updated in the following format:
- Updated By @mono/core: 0.0.1->0.0.2
  - feat: this is test @xxx · 2025-xx-xx · [#xxx](https://xxx)
  - feat: this is a test @xxx · 2025-xx-xx · [#xxx](https://xxx)

changeset_version

Accepts three optional parameters:

--no-git-push

Indicates that after bumping the version, it will not automatically push

--beta

No need to use changeset pre enter to enter and changeset pre exit to exit pre mode. Just use changeset_version --beta and it will increment version + 1 on each bump.

If --beta is not used, it will update to the release version

--filter

Indicates to only bump the version of certain packages, supports micromatch, for example: --filter @mono/changesets or --filter @mono/*

changeset_publish

Accepts one optional parameter:

--no-git-tag

Indicates that no tag will be created after publishing