wxt

Build cross-browser extensions with WXT file-based entrypoints and manifest generation.

9.0k|629|Updated Apr 16, 2025
One-click install
npx skills add https://github.com/mengxi-ream/read-frog --skill wxt-mengxi-ream
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: wxt
Source: https://github.com/mengxi-ream/read-frog/tree/main/.agents/skills/wxt
Command: npx skills add https://github.com/mengxi-ream/read-frog --skill wxt-mengxi-ream

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

WXT streamlines the complex task of building and maintaining browser extensions across multiple engines by providing a file-based entrypoint system, MV2/MV3 support, and a cohesive development workflow.

Core Features & Use Cases

  • File-based entrypoints and MV2/MV3-compatible builds for rapid extension development across Chrome, Firefox, Edge, and Safari.
  • Auto-imports, typed storage with migrations, content-script UIs, and modular extension components to speed up development and ensure type safety.
  • Supports multi-framework integrations and runtime configuration to manage manifest generation and cross-browser behavior.

Quick Start

Create a WXT project, configure an entrypoints layout, and run the dev server to see a multi-browser extension in action.

Frequently Asked Questions about wxt

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I build cross-browser extensions that support both MV2 and MV3?

You can build cross-browser extensions supporting MV2 and MV3 using WXT's file-based entrypoints. It streamlines manifest generation and deployment across Chrome, Firefox, Edge, and Safari from a single project configuration.

Can I use Vite for browser extension development with auto-imports?

Yes, WXT integrates Vite for browser extension development and provides auto-imports. This tooling integration accelerates development by automatically importing APIs and functions within your entrypoints and modules.

What is the best way to manage content scripts and typed storage in a web extension?

The best way to manage content scripts and typed storage in a web extension is using WXT. It offers typed storage with built-in migrations and content-script UIs to ensure type safety and maintainable code.

Does WXT support multiple frameworks for developing extension UIs?

Yes, WXT supports multi-framework integrations for developing extension UIs. It manages runtime configuration and cross-browser behavior, allowing you to use your preferred framework while generating the manifest automatically.

How do I configure entrypoints for a multi-browser extension?

You configure entrypoints for a multi-browser extension by defining a file-based layout in your WXT project. The framework automatically discovers these entrypoints and generates the manifest for your target browsers.

When do I need a modular ecosystem for browser extension development?

You need a modular ecosystem for browser extension development when managing complex features across multiple engines. WXT provides modular extension components and MV2/MV3 support to handle baseline features and cross-browser deployment robustly.