wxt-dev/wxt

Document entrypoint `PerBrowser` options

Open

#2304 opened on Apr 26, 2026

View on GitHub
 (0 comments) (2 reactions) (0 assignees)TypeScript (9,861 stars) (511 forks)user submission
contribution welcomedocsgood first issue

Description

This is an undocumented feature right now.

export default defineContentScript({
  matches: {
    chrome: ["..."],
    firefox: ["..."],
  },
  // ...
})

Contributor guide

Tech stack
typescript
Domain
documentation
Issue type
documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Basic TypeScriptUnderstanding of Web Extensions
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90
Research direction
Review the existing documentation for defineContentScript in the wxt repository. Look for where the `matches` option is documented and add a subsection for the `PerBrowser` pattern shown in the issue. Follow the style of existing documentation pages and consider adding an example similar to the one provided in the issue body.