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

vite-plugin-react-compiler-report

v0.1.1

Published

A Vite plugin that generates detailed reports for the React Compiler. It provides terminal logging during development and builds, and optionally generates a visual HTML report.

Readme

vite-plugin-react-compiler-report

A Vite plugin that generates detailed reports for the React Compiler. It provides terminal logging during development and builds, and optionally generates a visual HTML report.

Features

  • Dev Mode Logging: Real-time feedback in the terminal about compiled components and failures.
  • Build Report: Summary of optimization success rates at the end of the build.
  • HTML Report: A premium, dark-mode UI to explore compilation details and errors (optional).
  • Zero Config: Works out of the box with sensible defaults.

Installation

npm install -D vite-plugin-react-compiler-report
# or
pnpm add -D vite-plugin-react-compiler-report

Usage

  1. Configure the React Compiler in your Vite config (using babel options).
  2. Add the reactCompilerLogger passed to the compiler options.
  3. Add reactCompilerReport to your plugins list.
// vite.config.ts
import { defineConfig } from "vite";
import react from "@vitejs/plugin-react";
import { 
  reactCompilerLogger, 
  reactCompilerReport 
} from "vite-plugin-react-compiler-report";

const ReactCompilerConfig = {
  target: "19",
  logger: {
    logEvent: reactCompilerLogger,
  },
};

export default defineConfig({
  plugins: [
    react({
      babel: {
        plugins: [["babel-plugin-react-compiler", ReactCompilerConfig]],
      },
    }),
    reactCompilerReport({
      // Options
      ui: true, // Generate the HTML report
    }),
  ],
});

Configuration

You can customize the plugin by passing an options object:

reactCompilerReport({
  // Directory where reports will be generated
  // Default: ".react-compiler/report"
  outputDir: ".react-compiler/report",

  // Enable the HTML visual report
  // Default: false
  ui: true,
  
  build: {
    // Filename for the raw JSON report
    // Default: "react-compiler-report.json"
    fileName: "react-compiler-report.json"
  }
})

HTML Report

If ui: true is enabled, a static HTML report will be generated in outputDir/ui/index.html. The path to this file will be printed in the terminal at the end of the build.

You can open this file in any browser to inspect:

  • Total optimized components
  • Compilation failures
  • Detailed error messages and code locations