Weevar Compatibility

Frameworks#

React ≥ 17 (peer dependency)
react-dom ≥ 17 (peer dependency)
React 18 is the primary development target. Concurrent rendering and StrictMode have both been tested.
React 19 is supported; the Fiber-reading code paths have been validated against both major versions.

Weevar is not currently compatible with:

Vue - adapter planned for V2.
Svelte - adapter planned for V2.
Solid, Preact, Lit - not currently on the roadmap. Open an issue if interested.

Vite - first-class support via weevar/vite. The recommended path. Includes Tailwind detection and a virtual config module.
SWC (used by Next.js, custom SWC pipelines) - supported via weevar/swc. See SWC plugin →.
Webpack 5 - supported via weevar/webpack-loader. See Webpack loader →.
Turbopack - works as long as the JSX transform pipeline is intact, but no source-location plugin is provided yet.
No bundler plugin - works. Source location is unavailable; prompts fall back to DOM identity.

Primary validation target: Chromium-based browsers (Chrome, Edge, Brave, Arc).
Firefox / Safari: best-effort. The core overlay works; we haven't pushed for parity yet.

Development only. Weevar gates its runtime on process.env.NODE_ENV === 'development' and uses package exports conditions to resolve to a no-op stub in production.
No backend required. Weevar is fully client-side. It does not make network requests. Nothing leaves your machine unless you copy a prompt and paste it into a hosted AI tool.

Your source files. Weevar never writes to disk.
Your network. Weevar makes no network requests at runtime.
Your production bundle. The default exports condition resolves to a stub.
Other dev tools. Weevar coexists with React DevTools, Redux DevTools, the React Refresh runtime, and the standard browser DevTools inspector.