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

react-compiler-cli

v0.1.0

Published

Fast Rust CLI that reports which React files and components are processed by React Compiler.

Readme

react-compiler-cli

See what the React Compiler actually compiles — in milliseconds. A fast, Rust-powered auditor for projects adopting React Compiler. Zero config, monorepo-aware, AI-friendly output, with an MCP server for agents.

npx react-compiler-cli ai .
compiler: enabled=true mode=Infer source=vite.config.ts
stats: 301f 397c | enabled=397
issues: 29
  src/features/cart/Cart.tsx:42    CartList     [enabled] useMemo=1 useCallback=2
  src/features/checkout/Pay.tsx:18 PayButton    [enabled] React.memo
  ...

One command. Every component. Nothing to set up.


Install

npm i -g react-compiler-cli
# or:
npx react-compiler-cli ai .

Prebuilt binaries ship for darwin-arm64, darwin-x64, linux-x64, linux-arm64, linux-x64-musl (Alpine), and win32-x64. npm picks the right one automatically via optionalDependencies — no postinstall compile step, no Rust toolchain required.

What it does

  • scan — full structured report (JSON / text / Markdown) of every React file & component and whether the compiler processes it.
  • ai — compact digest optimized for LLM input. ~10× smaller than the full report.
  • doctor — verifies compiler config, lists workspaces, checks --deep availability.
  • cleanup — suggests (and optionally applies) removal of manual useMemo / useCallback that the compiler makes redundant.
  • MCP serverreact-compiler-mcp binary exposes all four as MCP tools for Claude Desktop, Cursor, and any MCP-capable agent.

Programmatic API

Import it in a Node script or CI check:

const { scan, ai, cleanup } = require("react-compiler-cli");

const report = await scan("./apps/web", { summary: true });
console.log(report.stats); // { enabled: 152, "opted-out-file": 3, ... }

const digest = await ai("./apps/web"); // compact JSON, LLM-ready
const hunks  = await cleanup("./apps/web"); // dry-run — pass { apply: true } to rewrite

All functions spawn the prebuilt binary and return parsed JSON (or the raw string when you pass format: "text" | "markdown"). binaryPath() returns the resolved binary path for custom spawns.

MCP integration

Point your agent at:

{
  "mcpServers": {
    "react-compiler": {
      "command": "npx",
      "args": ["-y", "react-compiler-mcp"]
    }
  }
}

Then ask “which components in this repo would benefit from removing manual memoization?” — grounded in your actual code.

Highlights

  • Orders of magnitude faster than Babel-based tools for coverage reports. Backed by oxc + rayon. Run bench/run.sh for numbers on your own tree — see README for the author's reference run.
  • Monorepo-nativepnpm-workspace.yaml, package.json#workspaces, mixed per-workspace compiler configs.
  • Detects everything: Vite / Next / Expo / Babel / SWC configs, "use memo" / "use no memo" / "use forget" directives, React.memo, forwardRef, annotation mode, and more.
  • --deep mode runs the real babel-plugin-react-compiler to confirm bailouts with reasons and spans.

Full documentation and examples: github.com/TheHypnoo/react-compiler-cli.

License

Licensed under either of MIT or Apache-2.0 at your option.

© TheHypnoo