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

@powerhousedao/ph-porter

v0.2.6

Published

CLI for migrating Powerhouse Reactor projects between stack versions and surfacing/fixing the issues a migration leaves behind.

Readme

@powerhousedao/ph-porter

CLI for migrating Powerhouse Reactor projects between stack versions and surfacing/fixing the issues a migration leaves behind.

Quick start

No install needed — invoke directly via your package manager:

cd /path/to/your/reactor-project
npx @powerhousedao/ph-porter migrate --version latest # migrate to latest

If you'd rather have a persistent install:

npm  install -g @powerhousedao/ph-porter

After that, ph-porter <command> works directly. Use ph-porter selfUpdate to bump it later.

Commands

All commands run against the current working directory unless --workdir <path> is passed. Pass --help to any command for full options.

  • status — inspects the project and reports its current state. Run this first when you walk into an unfamiliar project.
  • migrate <version> — migrates the project to the target stack version (e.g. latest, staging, dev, or an exact semver like 6.0.2). Destructive — requires a clean git working tree. Rollback with git restore ..
  • validate — runs lint, typecheck, build, and publint, then prints a per-step summary.
  • selfUpdate — updates the installed CLI to the latest npm version.

Interactive mode

Run ph-porter -i to interact with an agent. It can run the commands for you, read the output, and answer questions in plain language. You need to configure the model and API key to use.

| Setting | Description | Default | |---|---|---| | model | LLM model in provider/id form | anthropic/claude-haiku-4-5 | | anthropicApiKey | Anthropic API key | — |

Set them with the built-in config command:

ph-porter config --name anthropicApiKey --write sk-ant-...                # this project
ph-porter config --name anthropicApiKey --write sk-ant-... --scope user   # user-wide
ph-porter config --list                                                   # show all
ph-porter config --help                                                   # full reference

Use with an AI agent

This repo ships an Agent skill so AI agents, like Claude Code, can run ph-porter for you. Install it into the current project with:

npx skills add powerhouse-inc/ph-porter

After that, asking the agent to "migrate this reactor project" or "validate this powerhouse project" activates the skill.

Caveats

  • No dry-run. A clean git working tree is the rollback mechanism — git restore . undoes a failed migration.
  • Custom package.json exports are overwritten. migrate rewrites the exports field — re-apply any custom subpath exports afterwards.
  • Renamed or removed modules leave their old directories behind. Delete them by hand.

License

AGPL-3.0-only.