wxt-dev/wxt

Document entrypoint `PerBrowser` options

Closed

#2,304 opened on Apr 26, 2026

View on GitHubContributor guide
 (2 comments) (2 reactions) (0 assignees)TypeScript (511 forks)user submission
contribution welcomedocsgood first issue

Repository metrics

Stars
 (9,861 stars)
PR merge metrics
 (Avg merge 11d 22h) (51 merged PRs in 30d)

Description

This is an undocumented feature right now.

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

Contributor guide

Research direction
Review the existing code for the `defineContentScript` function to understand how the `PerBrowser` matches option works, and add documentation to the appropriate docs file.
Tech stack
typescript
Domain
frontend
Issue type
Documentation
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Git
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90