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

pnpm-category-catalog

v1.0.1

Published

A CLI tool for managing the pnpm workspace catalog, which helps you categorize the packages in the catalog and update the associated package.json reference.

Readme

English | 中文

pnpm-category-catalog is a CLI tool designed for monorepo projects using pnpm workspace. It solves the following pain points:

  • Batch Category Management: Process all dependencies in catalog at once, categorizing them by function or purpose
  • Automatic Reference Updates: Automatically update dependency references in package.json files of sub-projects to catalog:category-name format
  • Interactive Operations: Provide a friendly command-line interactive interface with confirm, cancel and undo support
  • Batch Processing: Support loop processing until all packages are categorized

🛠️ Usage

Prerequisites

  1. Project must use pnpm workspace.
  2. pnpm-workspace.yaml file must exist in the project root directory.
  3. pnpm-workspace.yaml file must contain catalog configuration.

📦 Best Practices

👀 Interested in pnpm catalogs? Recommend you read this post: Categorize Your Dependencies by Anthony.

Direct Execution

[!TIP] You can execute directly or install globally. The following examples use direct execution:

# 1. migrate to `pnpm catalog` (execute this command if not yet migrated).
pnpx codemod pnpm/catalog

# 2. execute custom category migration command.
npx pnpm-category-catalog

Global Usage

If you want to use the command globally, you can do this:

Global Installation

npm install -g pnpm-category-catalog
# or
pnpm add -g pnpm-category-catalog

Run

Run in the project root directory:

pcc

🔧 Extensions

ESLint Ecosystem

If you want to use ESLint for some constraints, you can choose one of the following methods (optional):

  1. If you are using @antfu/eslint-config
export default antfu({
    pnpm: true,
    // other options ...
})
  1. If you are not using @antfu/eslint-config, use it directly in eslint.config.js. For details, see: pnpm-workspace-utils

🤝 Contributing

Welcome to submit Issues and Pull Requests!

Development

# Install dependencies
pnpm install

# Run with example scenario (auto setup + run CLI)
pnpm dev:basic

Example Scenarios

| Command | Description | |------------------|------------------------------------------------------------| | pnpm dev:basic | Basic scenario: all deps in catalog, not yet categorized |

Each run automatically resets to initial state, so you can test repeatedly without pollution.

Directory Structure

examples/
├── fixtures/     # Original templates (read-only)
│   └── basic/
└── workspace/    # Working directory (auto-generated, git ignored)
    └── basic/

📄 License

MIT License © lonewolfyx