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

pnpm-dev-kit

v0.0.5

Published

PDK (pnpm dev kit), an efficient pnpm workspace development and publishing tool

Readme

Features

  • 💻 Dev Mode: Quickly launch on-demand development builds for monorepo packages
  • 🚀 Release Management: Automated version bumping and publishing
  • 🔧 Patch System: Repair failed package publications
  • 📝 Changelog Generation: Automatic, customizable changelog creation
  • 🏷️ GitHub Release: Automatic GitHub release creation with changelog extraction

Install

# Using npm
npm install --save-dev pnpm-dev-kit

# Using yarn
yarn add --dev pnpm-dev-kit

# Using pnpm
pnpm add -D pnpm-dev-kit

For global installation:

npm install -g pnpm-dev-kit

Usage

Development Mode

Quickly start development mode to build packages on demand when files change:

# Using the CLI
pdk dev

# Or with npm script
npm run dev

Interactive Features:

  • Type n to select a package to build manually
  • Type ps to list running processes
  • Type package name to build a specific package

Release Process

Standard Release:

# Complete release (recommended)
pdk release --push-tag --create-github-release

# Canary release for CI/CD
pdk release --canary

Release Flow:

  1. Select version type (patch/minor/major/prerelease)
  2. Choose NPM tag (latest/next/beta)
  3. Update workspace dependencies
  4. Publish packages to NPM
  5. Create git tag and push to remote
  6. Generate CHANGELOG.md
  7. Create GitHub Release

Failed Release Recovery:

pdk patch --version 1.0.0 --tag latest

Changelog Generation:

# Standard changelog
pdk changelog --version 1.0.0 --beautify --commit --git-push

# AI-powered changelog
pdk changelog --version 1.0.0 --use-ai --provider openai --model gpt-4o

GitHub Release:

pdk github-release --version 1.0.0
pdk github-release --dry-run  # Preview

Key Options:

  • --dry-run: Preview without changes
  • --run-in-band: Publish packages in series
  • --build: Custom build script before release
  • --ignore-scripts: Skip npm scripts
  • --auto-create-release-branch: Auto-create release branch
  • --filter-scopes: Filter by scope (default: tars,agent,tarko,o-agent,tars-stack,browser,infra,mcp,all)
  • --filter-types: Filter by commit type (default: feat,fix)

Configuration

package.json Scripts:

{
  "scripts": {
    "dev": "pdk dev",
    "release": "pdk release --push-tag",
    "release:full": "pdk release --push-tag --create-github-release",
    "release:canary": "pdk release --canary",
    "github-release": "pdk github-release",
    "changelog": "pdk changelog",
    "patch": "pdk patch --version $(node -p \"require('./package.json').version\") --tag latest"
  }
}

Workspace Setup:

  • Uses pnpm-workspace.yaml for package discovery
  • Follows conventional commit standards
  • Auto-updates internal workspace dependencies

CI/CD Integration:

# .github/workflows/release.yml
name: Release
on:
  push:
    tags:
      - 'v*'
jobs:
  release:
    runs-on: ubuntu-latest
    steps:
      - uses: actions/checkout@v3
      - uses: actions/setup-node@v3
        with:
          node-version: '18'
      - run: npm install -g pnpm
      - run: pnpm install
      - run: pnpm run release:full
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          NPM_TOKEN: ${{ secrets.NPM_TOKEN }}

Best Practices:

  • Always release from latest main branch
  • Ensure clean working directory
  • Run tests before release
  • Use --dry-run for testing
  • Canary format: {version}-canary-{commitHash}-{timestamp}
  • Auto-rollback on publish failure

License

This project is licensed under the Apache License 2.0.