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

@mlaursen/release-script

v0.1.0

Published

The release script I normally use for packages I publish to npm

Readme

@mlaursen/release-script

This is the normal npm release script I use. This requires:

  • changesets to handle bumping versions and generating changelogs.
  • A Github release token
    • The token only needs repository access
    • This is normally stored as GITHUB_TOKEN in an .env.local file that should not be committed

Installation

The release script relies on changesets to handle bumping versions and generating changelogs.

pnpm install --save-dev @mlaursen/release-script \
  @changesets/cli \
  tsx

Setup the .changeset dir if needed:

pnpm changeset init
git add .changeset
git add -u
git commit -m "build: setup changesets"

Usage

Create a scripts/release.ts file with:

import { release } from "@mlaursen/release-script";

await release({
  repo: "{{REPO_NAME}}", // i.e. eslint-config

  // if the repo is not under `mlaursen` for some reason
  // owner: "mlaursen",

  // If there is a custom clean command for releases. `clean` is the default
  // cleanCommand: "clean",

  // If there is a custom build command for releases. `build` is the default
  // buildCommand: "build",

  // An optional flag if the build step should be skipped. `!buildCommand` by default
  // skipBuild: process.argv.includes("--skip-build"),

  // If the version message needs to be customized. The following is the default
  // versionMessage: "build(version): version package",

  // An optional `.env` file path that includes the `GITLAB_TOKEN` environment
  // variable.
  // envPath: ".env.local",

  // An optional lookup of package name -> package path in the repo used to
  // find the CHANGELOG.md for each release in a monorepo. Will default to
  // `"."` when omitted.
  // packagePaths: {
  //   "@react-md/core": "./packages/core",
  // },
});

Next, update package.json to include the release script:

   "scripts": {
     "prepare": "husky",
     "typecheck": "tsc --noEmit",
     "check-format": "prettier --check .",
     "format": "prettier --write .",
     "clean": "rm -rf dist",
     "build": "tsc -p tsconfig.json",
+    "release": "tsx scripts/release.ts"
   },

Finally, run the release script whenever a new release should go out:

pnpm release

Adding Changesets

During normal development, add changesets and commit them. They will normally be close to my commit messages which is a bit annoying.

pnpm changeset
git add .changeset

Alpha Releases

Use the changesets api to enter the pre-release flow:

pnpm changeset enter pre

Once ready to do a real release:

pnpm changeset exit pre