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

@smplcty/release

v0.1.0

Published

Laptop-driven release tooling: derive the SemVer bump from CHANGELOG.md, cut prereleases correctly, and guard against a stale local branch. Shared across the simplicity/productionnow apps.

Readme

@smplcty/release

Shared, laptop-driven release tooling for the simplicity / productionnow apps. It keeps the version contract — the CHANGELOG section headings decide the SemVer bump — in one tested place, instead of drifting across hand-synced shell scripts.

What it does:

  • Derives the bump from CHANGELOG.md. ### Removed or **BREAKING** → major; ### Added → minor; otherwise patch.
  • Cuts prereleases correctly. --alpha/--beta/--rc/--preRelease=<id> advance the -alpha.N line (prerelease) or start one (pre<bump>) — never jumping a minor or dropping the tag. A malformed --preRelease errors instead of silently shipping a final release.
  • Guards against a stale branch. Fails fast (and fails closed) if local is behind its remote, before anything is built or tagged.

Install

pnpm add -D @smplcty/release release-it @release-it/keep-a-changelog

release-it and @release-it/keep-a-changelog are peer dependencies.

Usage

package.json:

"scripts": {
  "local-release": "smplcty-release",
  "local-ci": "./scripts/ci.sh"
}

.release-it.local.json (extend the shared preset, add your repo-specific bits):

{
  "extends": "@smplcty/release/configs/release-it.base.json",
  "git": { "requireBranch": "main" },
  "hooks": {
    "before:init": ["smplcty-release-preflight main", "pnpm local-ci"],
    "after:release": ["./scripts/release.sh"]
  }
}

release-it's extends deep-merges but replaces arrays, so before:init / after:release won't concat with the preset — that's why the generic preflight is a single command (smplcty-release-preflight) you list yourself.

Then:

pnpm local-release                 # final release; increment from the changelog
pnpm local-release --alpha         # staging prerelease (also --beta / --rc)
pnpm local-release --alpha --release-version   # print the next version and exit

CLIs

| Command | Purpose | | --- | --- | | smplcty-release | Run release-it with the changelog-derived / prerelease increment and the repo's local config. | | smplcty-release-preflight [branch] | before:init gate: clean tree + branch current + [Unreleased] has entries. | | smplcty-changelog-bump [path] | Print major/minor/patch for the [Unreleased] section (exits non-zero if empty). |

Library

import { computeBump, parseReleaseFlags, computeReleaseArgs, assertBranchCurrent } from '@smplcty/release';

All functions are pure (git access is injectable) and unit-tested — the tests are the executable spec for the version contract.