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

changeops

v1.0.0-prelresase.0

Published

DSC-driven release pipeline tool for operationalizing Changesets across repos and stacks

Readme

ChangeOps

⚠️ Read SETUP_REQUIREMENTS.md before contributing.

ChangeOps is a DSC-driven release pipeline tool for managing Changesets-based release workflows across platforms and build systems.

What it does

  • Multi-platform adapter model (github, ado, bitbucket, gitlab)
  • Multi-build-system adapter model (node, dotnet, aspire, react)
  • Desired-state config with validation (validate) and remote diagnostics (doctor)
  • Release model: promote, never rebuild

Install (normal usage)

# GitHub Packages auth is required (package is currently private during testing)
npm install --save-dev @kjldev/changeops

Run from your repository:

npx changeops validate
npx changeops doctor

Configuration

ChangeOps loads config from the first file it finds, in this order:

  1. .changeops/config.json (preferred)
  2. .changeops.config.json

Example:

{
  "version": "1.0",
  "platform": "github",
  "buildSystem": "node",
  "release": {
    "baseBranch": "main",
    "releaseBranchPattern": "releases/v*",
    "changesets": {
      "enabled": true,
      "enforcedOnPR": true,
      "bypassLabel": "no-changeset"
    }
  },
  "github": {
    "owner": "my-org",
    "repo": "my-repo"
  }
}

Environment variables in ${VAR_NAME} format are interpolated when config is loaded.

Commands

# Local validation (no API calls required)
npx changeops validate

# Pre-push style local branch check
npx changeops validate push

# Remote diagnostics (requires token for platform checks)
npx changeops doctor

# Pipeline setup preview/apply (in progress)
npx changeops setup --dry-run
npx changeops setup

init, sync, and release command paths exist but are not fully implemented yet.

Local development (this repository)

Use direct node bin/changeops.mjs ... commands only when developing ChangeOps itself:

npm ci
npm run lint
npm run build
npm test

node bin/changeops.mjs validate
node bin/changeops.mjs doctor

Development notes

  • Node.js 24+ required (package.json engines)
  • Package manager: npm
  • Test runner: Vitest (npm test, npm run test:ci)

Documentation