chrome-extension-wxt

WXT enables building Chrome extensions once and deploying across Chrome, Firefox, Edge, and Safari using Manifest V3. Initialize a project with npm create wxt@latest, configure your framework (React, Vue, Svelte, or Solid), and WXT handles cross-browser compatibility automatically through its file-based structure and build tooling.

Manifest V3 is Chrome's current standard, replacing the deprecated V2 with stricter security policies, service workers instead of background pages, and updated messaging APIs. WXT builds extensions following MV3 conventions by default, ensuring your extension meets modern browser requirements and future compatibility.

Yes. WXT supports React, Vue, Svelte, and Solid for UI integration in popup and content scripts. Choose your preferred framework during project initialization, and WXT scaffolds the entrypoint structure, type-safe storage, and messaging layer needed to connect your UI components to extension logic.

WXT provides type-safe messaging and storage APIs built into its framework. Define messages and storage keys in your configuration, and WXT generates typed utilities for communicating between background, content, and popup scripts, reducing runtime errors and improving maintainability across your extension.

WXT uses an entrypoint-based file structure where background scripts, content scripts, and popups live in dedicated directories with automatic discovery. Your wxt.config.ts defines manifest settings, and the framework compiles these files into a production-ready extension with proper module resolution and bundling.

No. WXT generates manifest.json from your wxt.config.ts configuration file. This approach keeps your Manifest V3 settings centralized, typed, and synchronized with your code structure, eliminating manual JSON editing and reducing configuration drift.