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

@iteraai/vite-plugin-react-inspector

v0.1.2

Published

Vite plugin that injects the Itera React component inspector runtime into React-Vite apps.

Readme

@iteraai/vite-plugin-react-inspector

Vite plugin for injecting the Itera React component inspector runtime into React-Vite apps.

This package is the React-Vite integration surface for the Itera inspector. It reuses @iteraai/react-component-inspector and @iteraai/inspector-protocol; it does not replace the existing bridge or iteration runtime.

Installation

npm install @iteraai/vite-plugin-react-inspector @vitejs/plugin-react

Your app should already provide React and React DOM:

  • react: ^18.3.0 || ^19.0.0
  • react-dom: ^18.3.0 || ^19.0.0

Manual React-Vite Usage

import react from '@vitejs/plugin-react';
import { defineConfig } from 'vite';
import { createIteraReactInspectorVitePlugin } from '@iteraai/vite-plugin-react-inspector';

export default defineConfig({
  plugins: [createIteraReactInspectorVitePlugin(), react()],
});

Enable it for local testing with Vite environment variables:

VITE_ITERA_COMPONENT_INSPECTOR_ENABLED=true \
VITE_ITERA_COMPONENT_INSPECTOR_HOST_ORIGINS=https://app.iteradev.ai \
npm run dev

You can also configure it directly:

createIteraReactInspectorVitePlugin({
  enabled: true,
  hostOrigins: ['https://app.iteradev.ai'],
});

By default, the plugin only injects the runtime for Vite serve/dev mode. For an explicit local preview build, opt in to build HTML injection:

createIteraReactInspectorVitePlugin({
  enabled: true,
  hostOrigins: ['https://app.iteradev.ai'],
  includeInBuild: true,
});

Do not enable includeInBuild for normal production builds unless the build output is specifically intended to carry the inspector runtime.

API

createIteraReactInspectorVitePlugin(options?: {
  enabled?: boolean;
  hostOrigins?: readonly string[] | string;
  includeInBuild?: boolean;
})

The package also exports iteraReactInspector as a shorter alias for the same factory.

The plugin-generated virtual module imports @iteraai/vite-plugin-react-inspector/client as a small browser runtime support entry. Application code should normally use the plugin factory instead of importing the client entry directly.

When enabled is omitted, the plugin enables only when VITE_ITERA_COMPONENT_INSPECTOR_ENABLED is exactly true. Host origins can come from hostOrigins or the comma-separated VITE_ITERA_COMPONENT_INSPECTOR_HOST_ORIGINS value.

If the inspector is enabled but no trusted host origins are available, the plugin warns and does not inject or start the bridge.