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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@g-tests/changeset-tests

v0.0.3

Published

### Standard public package template.

Downloads

7

Readme

@changesets/cli Github action.

Standard public package template.

@see Publish

  • Make sure that the NPM_TOKEN is not expired.
  • Make sure that "Allow GitHub Actions to create and approve pull requests" is checked.
  • Make sure that package.json file has "publishConfig": { "access": "public" }, and remove "private": "false" if present.
  • Make sure that .changeset/config.json file has "access": "public"
  • Make sure that the installed version of your package manager is the same in .github/workflows YML files with the used version in your local.
  • Run pnpm changeset every time you need to update your package version, before commiting and pushing to Github repository and changesets/action will handle version.
  • Every PR is opened by Chengesets release Github action will create a head branch changeset-release/main, which can be deleted automatically after merge by activate "Automatically delete head branches" in the repo general settings.
  • Every mergrd PR has been opened by Changesets release Github action will create a tag/release/publish to NPM registry

@see changeset-tests NPM package

That's a standard configuration. For more information, visit Changesets