CLI tool
wxt-dev/wxt avatar
wxt-dev/wxt

WXT is a Nuxt for browser extensions, and its own tests run against a fake browser

⚡ Next-gen Web Extension Framework

10,738 stars588 forksTypeScriptMIT

At a glance

What is it?
WXT is a TypeScript framework for writing browser extensions, built on the idea that entrypoints should be files and imports should be automatic. The README is short, so most of the decision rests on the docs site, and on the fact that the project's test suite exercises a fake browser rather than a real one.
Who is it for?
WXT fits teams shipping Chrome and Firefox extensions at the same time who want a file layout and auto-imports instead of a hand-maintained manifest. It does not fit a team that needs the configuration surface documented in the repository itself, because the README carries no config keys and no example entrypoint tree; both live at wxt.dev.
Can I use it commercially?
Yes. MIT is a permissive licence: you can use, modify and sell software built on it, as long as you keep its copyright and licence notices.
Is it still maintained?
Yes. The repository received new commits within the last day.
What is it written in?
Mainly TypeScript, according to GitHub's language statistics.

Answers come from the project's GitHub data, last synced on November 16, 2026, and from our analysis. They are not legal advice.

From daily snapshots

Star history

  • wxt-dev/wxt10,738 ★ · +206
Star history
Repository2026-09-222026-11-16
wxt-dev/wxt10.5k10.7k

206 Stars in the last 55 days, measured from the daily GitHub snapshot. Compare with other projects

Editorial analysis

Three package managers run the same init command

The Quick Start section is the whole bootstrap story, and it fits in one block:

sh
# npm
npx wxt@latest init

# pnpm
pnpm dlx wxt@latest init

# bun
bunx wxt@latest init

The point worth noticing is the @latest tag. None of these pins a version, so a fresh project starts from whatever the registry served when you ran the command. Pin it yourself if you intend to reproduce that project later.

For anything beyond the scaffold, the README sends you to the installation guide at wxt.dev/guide/installation.html and to a configuration reference at wxt.dev/api/reference/wxt/interfaces/inlineconfig.html. The repository itself stops at the one command. That is the shape of the project: a landing page that gets you running and a documentation site that carries the actual decisions.

File based entrypoints, and no example of one in the README

File based entrypoints and auto-imports are two of the features the README lists: the project describes itself as like Nuxt, but for Web Extensions.

The comparison explains the design and also its cost. A Nuxt-style framework derives much of a build from conventions, which removes hand-written plumbing and adds a layer you have to learn before you can change anything outside the happy path. What the README does not do is show the directory layout it expects. There is no file tree, no sample entrypoint, and no naming rule here. Anyone deciding whether WXT fits an existing repository has to open the examples page or the installation guide to see how files map to the extension manifest, and that check should happen before the scaffold, not after.

MV2 and MV3 in one project, with dev mode hot reload

The feature list claims two things that matter to a rollout: it supports all browsers, and it supports both MV2 and MV3. Those two claims are related but not the same. Supporting both manifest versions means one project can target MV2 and MV3, and supporting all browsers is what lets one codebase serve Chrome, Firefox and the rest.

Development is where a framework earns its keep, and the README claims dev mode with HMR and fast reload. Hot module replacement inside an extension is harder than in a web page because the extension context is torn down and reloaded, so this is the claim to verify early rather than late. The README gives no command for starting dev mode, no list of what reloads in place and what triggers a full extension reload, and no note on which browsers it was checked against. Budget a day to confirm that behaviour on your own target browsers before scheduling around it.

The framework agnostic claim covers Vue, React and Svelte

Frontend framework agnostic is listed as a feature, with Vue, React and Svelte named as examples. In practice this means WXT does not force a view layer on your extension, which matters because most extensions ship a small popup or options page and little else.

The dependency catalog in the root package.json lists @types/react at ^19.2.14 and @types/react-dom at ^19.2.3.

Bundle analysis is listed as a feature too, which fits that crowd: extension size limits push people to check what landed in the package before shipping, and a framework that can report bundle composition removes a manual step.

Contributing to WXT means Bun workspaces, TypeDoc and VitePress

The root package.json is private and declares its workspaces and engine requirement:

json
  "engines": {
    "bun": ">=1.4.4"
  },

The workspaces field points at packages/*, and the scripts assume a Bun toolchain:

json
  "scripts": {
    "check": "bun run cspell-order:check && check && bun run --sequential --workspaces check",
    "test": "bun run --workspaces test run",
    "test:coverage": "bun run --workspaces test:coverage",
    "prepare": "simple-git-hooks",
    "docs:gen": "typedoc --options docs/typedoc.json",
    "docs:dev": "bun run --silent docs:gen && bun run --bun vitepress dev docs",
    "docs:build": "bun run --silent docs:gen && bun run --bun vitepress build docs",
    "docs:preview": "bun run --silent docs:gen && bun run --bun vitepress preview docs"
  },

Read that as two audiences. If you consume WXT, none of it applies; you install the wxt package through a package manager. If you fork it, you need Bun 1.4.4 or newer, and the docs you read are generated from source by TypeDoc and served by VitePress. A netlify.toml in the root is there to deploy that site, and a patches/ directory next to bun.lock means the maintainers patch some dependencies rather than building around them. Contributors inherit that work.

The test suite exercises a fake browser, not a real one

The dependency catalog includes @webext-core/fake-browser at ^1.3.4, alongside vitest at ^4.1.10 and a v8 coverage package. That combination suggests how the project's own tests run: extension APIs are answered by a fake implementation, in process, under Vitest.

That is a reasonable way to keep unit tests fast, and it is also a limit you should know about. A fake browser cannot tell you that a permission prompt behaves differently in one browser than another, and it does not reproduce the load order of a real extension at install time. Nothing in the README documents which browsers the framework has been verified against, so the gap between what the test suite exercises and what your users run is not recorded anywhere you can read here.

The practical consequence: keep your own smoke tests on real browsers. A framework whose tests pass tells you your logic holds against the specification surface it mocks, not that the extension installs and runs in the browser your users have.

Automated publishing is a listed feature with no documented credentials path

Automated publishing appears in the feature list, and a module system is offered for reusing code between extensions. The module system is described as being for reusing code between extensions.

Neither is documented in the README. There is no description of where signing keys or store credentials are supplied, no command shown for a publish run, and no statement about which stores are supported. The changelog lives at packages/wxt/CHANGELOG.md, which implies a monorepo where several packages move independently, and the recent releases confirm it: wxt v0.21.5 on 2026-10-26, @wxt-dev/analytics v0.5.8 the same day, and @wxt-dev/storage v1.3.0 on 2026-10-04.

Those three numbers are a warning for anyone pinning dependencies. The framework sits below 1.0 while one of its modules is already past 1.0, so a module's major version tells you nothing about the framework version it belongs to. Check each package separately when you lock your build.

Editorial conclusion

WXT fits teams shipping Chrome and Firefox extensions at the same time who want a file layout and auto-imports instead of a hand-maintained manifest. It does not fit a team that needs the configuration surface documented in the repository itself, because the README carries no config keys and no example entrypoint tree; both live at wxt.dev. Before adopting, check the configuration reference at https://wxt.dev/api/reference/wxt/interfaces/inlineconfig.html against the browsers you ship to, and run your extension against a real browser, since WXT's own tests use the fake-browser package rather than a live one. The last push was on 2026-11-02, with the wxt package last released as v0.21.5 on 2026-10-26.

Frequently asked questions

What are the benefits of WXT?

The README lists support for all browsers, both MV2 and MV3, dev mode with HMR and fast reload, file based entrypoints, TypeScript, auto-imports, automated publishing, frontend framework agnostic use with Vue, React and Svelte, a module system, quick project bootstrap and bundle analysis.

How do I install WXT?

Bootstrap a project with npx wxt@latest init, pnpm dlx wxt@latest init or bunx wxt@latest init, all tagged @latest. The README also links an installation guide at https://wxt.dev/guide/installation.html.

Does WXT work with React and Vue?

The README describes WXT as frontend framework agnostic and says it works with Vue, React, Svelte and others, so you bring your own component layer instead of adopting one through the framework.

Which manifest versions and browsers does WXT target?

The feature list states that WXT supports all browsers and supports both MV2 and MV3. The README does not enumerate a specific browser list or version requirements.

Where is WXT configured?

Configuration is documented at https://wxt.dev/api/reference/wxt/interfaces/inlineconfig.html, which the README links as its Configuration reference. The README itself shows no configuration keys or example file.

Official sources

  1. License: MIT
  2. Project website
  3. README
  4. Releases
  5. wxt-dev/wxt on GitHub
Add this badge to your README

If you maintain this project, the badge below links readers to this analysis and shows its maintenance status from the daily GitHub snapshot. Paste the markdown into your README; add ?metric=license or ?metric=stars to the image URL for a different field.

Add this badge to your README

markdown
[![Hysen Labs](https://hysenlabs.com/badge/wxt-dev-wxt.svg)](https://hysenlabs.com/projects/wxt-dev-wxt)

Star history chart for your README

markdown
[![Star history](https://hysenlabs.com/chart/wxt-dev-wxt.svg)](https://hysenlabs.com/projects/wxt-dev-wxt)

Was this useful?