Registry / http-networking / vite-bridge

vite-bridge

JSON →
library1.1.5jsnpmunverified

A Vite plugin that bridges React applications with Kulp.AI, providing error reporting, route tracking, component tagging, and postMessage-based communication. Current stable version is 1.1.5, with no established release cadence. Key differentiators: development-only operation, configurable bridges, TypeScript support, and dependency on @babel/parser, magic-string, and estree-walker for component tagging. Alternatives include custom Vite plugins for similar features, but vite-bridge offers a unified integration with Kulp.AI.

npm install vite-bridge
INSTALL
IMPORT
SIG · VITE-BRIDGE
V
vite-bridge
http-networkingjavascriptv1.1.5
Install
Import
Disk
Pass rate
0/ 6
Env Coverage0 / 6
glibc
1822
musl
1822
Install & Compatibility
Where this runs
tested against v? · npm install
Install × environment matrix
Each cell = how many times install + import succeeded across repeated harness runs. Partial = flaky.
glibc = Debian/Ubuntu slim · musl = Alpine Linux
musl
node 18223 runs
build_error
glibc
node 18223 runs
build_error
Code
Verified usage

Verified import paths — ran on the pinned version, not inferred.

viteBridge
import { viteBridge } from 'vite-bridge'
import viteBridge from 'vite-bridge'
viteBridge is a named export, not a default export.
ViteBridgeOptions
import type { ViteBridgeOptions } from 'vite-bridge'
import { ViteBridgeOptions } from 'vite-bridge'
Type imports should use the type keyword for TypeScript.
BuildError
import type { BuildError } from 'vite-bridge'
import { BuildError } from 'vite-bridge'
BuildError is a TypeScript interface, not a runtime value.

Shows basic setup of vite-bridge plugin in Vite configuration with all bridges enabled.

import { defineConfig } from 'vite'; import { viteBridge } from 'vite-bridge'; export default defineConfig({ plugins: [ ...viteBridge(), ], });
Debug
Known issues
gotchaNote: viteBridge() returns an array of plugins, so you need to spread the result with '...viteBridge()'.
fix
Use ...viteBridge() instead of viteBridge() as a single plugin.
affects: >=1.0.0
gotchaComponent tagger requires additional dependencies: @babel/parser, magic-string, and estree-walker. If missing, the feature is silently disabled.
fix
Install the required dependencies: npm install @babel/parser magic-string estree-walker
affects: >=1.0.0
gotchaTailwind CSS configuration generation requires esbuild and tailwindcss to be installed separately.
fix
Install optional dependencies: npm install esbuild tailwindcss
affects: >=1.0.0
deprecatedNo known deprecations in v1.1.5.
fix
N/A
affects: >=1.0.0
Errors
Common errors & fixes
Cannot find module '@babel/parser' or its corresponding type declarations.
Missing required dependency for component tagger.
fix
npm install @babel/parser
TypeError: viteBridge is not a function
Incorrect import or spread missing.
fix
Ensure you use 'import { viteBridge } from 'vite-bridge'' and spread the result: '...viteBridge()'
Attempted import error: 'viteBridge' is not exported from 'vite-bridge'.
Using default import instead of named import.
fix
Change to 'import { viteBridge } from 'vite-bridge''
Upgrade
Version history
1.1.5latest on npm
Audit
Dependencies

No dependency data recorded yet.

Agent activity
38 hits · last 30 days
node
32
OpenAI (training)
1
Resources
vite-bridge — npm install vite-bridge · libregistry