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

@ic-reactor/vite-plugin

v0.9.0

Published

Vite plugin for zero-config IC reactor generation from Candid files

Downloads

1,191

Readme

@ic-reactor/vite-plugin

Vite plugin for IC Reactor code generation. It runs the shared @ic-reactor/codegen pipeline, watches .did files, and can inject the ic_env cookie used by ClientManager during local development.

Install

pnpm add -D @ic-reactor/vite-plugin
pnpm add @ic-reactor/react @tanstack/react-query @icp-sdk/core

Quick Start

// vite.config.ts
import { defineConfig } from "vite"
import react from "@vitejs/plugin-react"
import { icReactor } from "@ic-reactor/vite-plugin"

export default defineConfig({
  plugins: [
    react(),
    icReactor({
      canisters: [{ name: "backend", didFile: "./backend/backend.did" }],
    }),
  ],
})
// src/clients.ts
import { ClientManager } from "@ic-reactor/react"
import { QueryClient } from "@tanstack/react-query"

export const queryClient = new QueryClient()
export const clientManager = new ClientManager({
  queryClient,
  withCanisterEnv: true,
})

The plugin generates files under src/declarations/<canister>/ by default.

If you want non-React output, set target: "core" and install the matching runtime package instead of @ic-reactor/react.

Options

icReactor({
  canisters: [
    {
      name: "backend",
      didFile: "./backend/backend.did",
      mode: "DisplayReactor",
    },
  ],
  outDir: "src/declarations",
  clientManagerPath: "../../clients",
  target: "react",
  injectEnvironment: true,
})

Per-canister options

  • name
  • didFile
  • outDir
  • clientManagerPath
  • target
  • mode
  • canisterId

Supported mode values:

  • Reactor
  • DisplayReactor
  • CandidReactor
  • CandidDisplayReactor
  • MetadataDisplayReactor

Supported target values:

  • react (default): generates the reactor plus bound React hooks
  • core: generates only the typed reactor exports with no React dependency

Local Development Behavior

When injectEnvironment is enabled during vite dev, the plugin:

  1. asks icp-cli for the local network status
  2. resolves configured canister IDs
  3. sets the ic_env cookie
  4. proxies /api to the local replica

If environment detection fails, the plugin still falls back to proxying /api to http://127.0.0.1:4943, but it will not inject canister metadata.

File Regeneration

On startup and on .did file changes, the plugin regenerates declarations and the managed index.generated.ts implementation. The user-facing index.ts entry is created once, then preserved unless it still matches the default wrapper or a legacy generated scaffold that can be migrated automatically. When a watched .did file changes, the plugin sends a full browser reload so the new declarations are picked up.

When To Use It

  • Vite apps with active .did iteration
  • teams that want zero extra codegen commands during development
  • projects that want the same output format as the CLI without manual steps

See Also

  • Docs: https://ic-reactor.b3pay.net/v3/packages/vite-plugin
  • @ic-reactor/codegen: ../codegen/README.md
  • @ic-reactor/cli: ../cli/README.md