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

@usephase/codemod

v0.1.0

Published

Versioned migrations for phase packages

Readme

@usephase/codemod

Versioned migrations for phase packages.

Status: Alpha. Review all changes before committing them.

Each migration is a subcommand named for its source and destination. Published subcommands keep their original behavior, so teams can run the same migration later.

Available codemods

| Codemod | From | To | Purpose | | ------------------------------------------------------------------------------------------------------------------------------------ | -------------- | --------------------------------------------------- | ------------------------------------------------------------------------ | | migrate-phase-to-usephase | phase <0.6.0 | @usephase/core ^0.6.0@usephase/react ^0.6.0 | Move legacy runtime imports and package metadata to the scoped packages. |

The linked guide explains what each codemod changes and any limits that apply.

Run a codemod

npx @usephase/codemod@latest <codemod> [--dry] <path>
  1. Start from a clean Git worktree.
  2. Run with --dry and read the report.
  3. Run again without --dry.
  4. Review the diff.
  5. Run your package manager. Codemods do not edit lockfiles.

Safety

  • --dry writes nothing.
  • Discovery and parsing finish before writes begin.
  • Each changed file is replaced atomically.
  • If a later write fails, the report lists completed files. Rerunning is safe.

Exit codes

| Code | Meaning | | ---- | --------------------------------- | | 0 | Help shown or migration succeeded | | 1 | Read, parse, or write failure | | 2 | Invalid invocation or target |

Requirements

Node.js 22.12.0 or later.