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

@llm-ports/migrate

v0.1.0-alpha.20.1

Published

Codemods for migrating consumer code across @llm-ports/* alpha releases. Conservative, best-effort, runs offline.

Readme

@llm-ports/migrate

Codemods for moving consumer code across @llm-ports/* alpha releases.

Each codemod is conservative: it rewrites only patterns where the fix is unambiguous, prints a manual-review notice for ambiguous matches, and defaults to dry-run. Always review the diff before committing.

Install + run

# Preview the diff (dry-run is the default):
npx @llm-ports/migrate@alpha alpha-19-to-alpha-20

# Apply the rewrites in place:
npx @llm-ports/migrate@alpha alpha-19-to-alpha-20 --write

# Scan a specific directory (default: current working directory):
npx @llm-ports/migrate@alpha alpha-19-to-alpha-20 ./apps/web --write

# List all available migrations:
npx @llm-ports/migrate@alpha --list

Available migrations

alpha-19-to-alpha-20

Rewrites reads of <expr>.budgetLimit.requestsPerHour to add ?? Infinity, closing the strict-mode TypeScript breakage introduced by alpha.20 (the field went from required to optional). Conservative: skips matches already followed by ? (optional chaining or nullish coalescing), skips assignments, flags matches inside if ( conditions and on assignment LHS as manual-review.

Example:

- const rph = entry.budgetLimit.requestsPerHour;
+ const rph = (entry.budgetLimit.requestsPerHour ?? Infinity);

See docs/migration/alpha-19-to-alpha-20.md for the full migration page.

Programmatic use

import { runMigration, listMigrations } from "@llm-ports/migrate";

const report = await runMigration("alpha-19-to-alpha-20", {
  root: "./src",
  write: true,
});

console.log(report);
// { filesScanned: 42, filesChanged: 3, rewritesApplied: 5, manualReviewSites: [] }

License

MIT.