chore(release): wxt v0.21.2

BREAKING CHANGE: Updates `.wxt/tsconfig.json` defaults to latest recommended settings for vite projects and requires Typescript 5.4 or later. See #2512 for details on what compiler options were changed.

Co-authored-by: cookesan <cookesan@users.noreply.github.com>

.commitlintrc.yml

@@ -0,0 +1,10 @@
+extends:
+  - '@commitlint/config-conventional'
+rules:
+  subject-case:
+    - 0
+    - always
+    - - sentence-case
+      - start-case
+      - pascal-case
+      - upper-case

.gitattributes

@@ -1,5 +1,17 @@
+# See https://git-scm.com/docs/gitattributes#_pattern_format for more about `.gitattributes`.
+
+# Normalize EOL for all files that Git considers text files
 * text=auto eol=lf
+
+# Mark lock files as generated to avoid diffing
 pnpm-lock.yaml linguist-generated
 package-lock.json linguist-generated
 bun.lockb linguist-generated
+bun.lock linguist-generated
 yarn.lock linguist-generated
+
+# Exclude templates from language statistics
+templates/**/* linguist-vendored
+
+# Other generated files
+packages/browser/src/gen/** linguist-generated

.github/CODEOWNERS

@@ -0,0 +1,12 @@
+# Set default
+* @aklinker1
+
+# Secure Directories
+/.github/ @aklinker1
+
+# Creator of specific wxt modules
+/packages/auto-icons/ @Timeraa
+/packages/unocss/ @Timeraa
+
+# Other Directories
+/docs @aklinker1 @PatrykKuniczak @nishu-murmu

.github/FUNDING.yml

@@ -0,0 +1,3 @@
+# https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/displaying-a-sponsor-button-in-your-repository#about-funding-files
+
+github: wxt-dev

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -1,6 +1,7 @@
 name: "\U0001F41E Bug report"
 description: Report an issue with WXT
 labels: [pending-triage]
+type: Bug
 body:
   - type: markdown
     attributes:

.github/ISSUE_TEMPLATE/feature_request.md

@@ -2,7 +2,7 @@
 name: Feature request
 about: Suggest an idea for WXT
 title: ''
-labels: feature
+type: Feature
 assignees: ''
 ---
 

.github/actions/setup/action.yml

@@ -1,17 +1,21 @@
 name: Basic Setup
-description: Install PNPM, Node, and dependencies
+description: Install Bun and dependencies
+
+inputs:
+  install:
+    default: 'true'
+    description: Whether or not to run 'bun install'
+
 runs:
   using: composite
+
   steps:
-    - name: Setup PNPM
-      uses: pnpm/action-setup@v3
+    - name: 🛠️ Setup Bun
+      uses: oven-sh/setup-bun@735343b667d3e6f658f44d0eca948eb6282f2b76 # v2.0.2
       with:
-        version: 8
-    - name: Setup NodeJS
-      uses: actions/setup-node@v4
-      with:
-        node-version: 18
-        cache: pnpm
-    - name: Install Dependencies
+        bun-version-file: '.tool-versions'
+
+    - name: 📦 Install Dependencies
+      if: ${{ inputs.install == 'true' }}
       shell: bash
-      run: pnpm install
+      run: bun ci ${{ inputs.installArgs }}

.github/dependabot.yml

@@ -1,15 +1,20 @@
-# To get started with Dependabot version updates, you'll need to specify which
-# package ecosystems to update and where the package manifests are located.
-# Please see the documentation for all configuration options:
 # https://docs.github.com/github/administering-a-repository/configuration-options-for-dependency-updates
-
 version: 2
 updates:
-  - package-ecosystem: npm
-    directory: '/' # Location of package manifests
+  - package-ecosystem: bun
+    directory: /
     schedule:
-      interval: 'monthly'
+      interval: 'daily'
+      groups:
+        production-updates:
+          applies-to: version-updates
+          dependency-type: production
+          update-types: [minor, patch]
+        dev-updates:
+          applies-to: version-updates
+          dependency-type: development
+          update-types: [minor, patch]
   - package-ecosystem: 'github-actions'
     directory: '/'
     schedule:
-      interval: 'monthly'
+      interval: 'daily'

.github/pull_request_template.md

@@ -0,0 +1,13 @@
+### Overview
+
+<!-- Describe your changes and why you made them -->
+
+### Manual Testing
+
+<!-- Describe how to test your changes to make sure the PR works as intended -->
+
+### Related Issue
+
+<!-- If this PR is related to an issue, please link it here -->
+
+This PR closes #<issue_number>

.github/workflows/auto-label.yml

@@ -0,0 +1,115 @@
+name: ✨ Auto-label PR
+
+on:
+  pull_request_target:
+    types: [opened, synchronized, reopened]
+
+jobs:
+  update-pr:
+    name: Update PR
+    runs-on: ubuntu-latest
+    permissions:
+      pull-requests: write
+    steps:
+      - name: Gather Info
+        id: check
+        uses: actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0
+        with:
+          script: |
+            const { data: pr } = await github.rest.pulls.get({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              pull_number: context.payload.pull_request.number
+            });
+
+            // Check if PR has assignees
+            const hasAssignees = pr.assignees && pr.assignees.length > 0;
+            core.setOutput('has_assignees', hasAssignees);
+            core.setOutput('author', pr.user.login);
+
+            // Get list of changed files
+            const { data: files } = await github.rest.pulls.listFiles({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              pull_number: context.payload.pull_request.number
+            });
+
+            // Find all packages that were modified
+            const packagesRegex = /^packages\/([^\/]+)\//;
+            const affectedPackages = new Set();
+
+            for (const file of files) {
+              const match = file.filename.match(packagesRegex);
+              if (match) {
+                affectedPackages.add(match[1]);
+              }
+            }
+
+            const labels = Array.from(affectedPackages).map(pkg => `pkg/${pkg}`);
+            core.setOutput('labels', JSON.stringify(labels));
+            console.log('Detected package labels:', labels);
+
+            // Get current labels on the PR that match pkg/* pattern
+            const currentPkgLabels = pr.labels
+              .map(label => label.name)
+              .filter(name => name.startsWith('pkg/'));
+
+            core.setOutput('current_pkg_labels', JSON.stringify(currentPkgLabels));
+            console.log('Current pkg labels:', currentPkgLabels);
+
+      - name: Sync Author
+        if: steps.check.outputs.has_assignees == 'false'
+        uses: actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0
+        with:
+          script: |
+            try {
+              await github.rest.issues.addAssignees({
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                issue_number: context.payload.pull_request.number,
+                assignees: ['${{ steps.check.outputs.author }}']
+              });
+
+              console.log('Assigned PR author: ${{ steps.check.outputs.author }}');
+            } catch (err) {
+              console.warn("Error assigning author:", err);
+            }
+
+      - name: Sync Labels
+        uses: actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0
+        with:
+          script: |
+            const newLabels = ${{ steps.check.outputs.labels }};
+            const currentLabels = ${{ steps.check.outputs.current_pkg_labels }};
+
+            // Find labels to add (in newLabels but not in currentLabels)
+            const labelsToAdd = newLabels.filter(label => !currentLabels.includes(label));
+
+            // Find labels to remove (in currentLabels but not in newLabels)
+            const labelsToRemove = currentLabels.filter(label => !newLabels.includes(label));
+
+            // Add new labels
+            if (labelsToAdd.length > 0) {
+              await github.rest.issues.addLabels({
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                issue_number: context.payload.pull_request.number,
+                labels: labelsToAdd
+              });
+              console.log('Added labels:', labelsToAdd);
+            }
+
+            // Remove obsolete labels
+            for (const label of labelsToRemove) {
+              await github.rest.issues.removeLabel({
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                issue_number: context.payload.pull_request.number,
+                name: label
+              });
+              console.log('Removed label:', label);
+            }
+
+            if (labelsToAdd.length === 0 && labelsToRemove.length === 0) {
+              console.log('No label changes needed');
+            }

.github/workflows/notify-unreleased-commits.yml

@@ -0,0 +1,36 @@
+name: 🔔 Notify Unreleased Commits
+on:
+  workflow_dispatch:
+  schedule:
+    - cron: '0 20 * * 1' # Weekly at 8 PM UTC (3 PM CT)
+
+jobs:
+  notify:
+    runs-on: ubuntu-22.04
+    if: github.repository_owner == 'wxt-dev'
+    steps:
+      - name: Checkout
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
+        with:
+          fetch-depth: 0
+
+      - name: List Commits
+        id: list-commits
+        run: |
+          ./scripts/list-unreleased-commits.sh > summary.txt
+
+      - name: Discord notification
+        run: |
+          PAYLOAD=$(jq -n --arg content "${{ env.MESSAGE }}" '{"content": $content}')
+          curl -X POST \
+            -F "payload_json=${PAYLOAD}" \
+            -F "file1=@summary.txt" \
+            $DISCORD_WEBHOOK
+        env:
+          DISCORD_WEBHOOK: ${{ secrets.DISCORD_WEBHOOK_UNRELEASED_COMMITS }}
+          MESSAGE: |
+            If a package needs released, please [run the workflow](<https://github.com/wxt-dev/wxt/actions/workflows/release.yml>).
+
+            Before running, consider:
+            - Are there any breaking changes? If so, prepare a list of breaking changes and update the changelog and release notes after the release.
+            - Are there any PRs open that we wait to release after they're merged?

.github/workflows/pkg.pr.new.yml

@@ -0,0 +1,34 @@
+name: ✨ pkg.pr.new
+on:
+  push:
+    branches:
+      - main
+  pull_request:
+    branches:
+      - main
+
+permissions:
+  contents: read
+
+jobs:
+  build:
+    name: Publish Test Packages
+    runs-on: ubuntu-22.04
+    if: ${{ github.repository == 'wxt-dev/wxt' }}
+    steps:
+      - name: Checkout
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
+
+      - name: Setup
+        uses: ./.github/actions/setup
+
+      - name: Build All Packages
+        run: bun run buildc all
+
+      - name: Publish
+        run: bunx pkg-pr-new publish --compact --bun './packages/*'
+
+      - name: DEBUG
+        if: always()
+        run: ls -lhA
+        working-directory: packages/analytics

.github/workflows/pr-closed.yml

@@ -0,0 +1,43 @@
+name: 🎉 PR closed
+
+on:
+  pull_request_target:
+    types:
+      - closed
+
+permissions:
+  contents: read
+  pull-requests: write
+
+jobs:
+  thank-you:
+    runs-on: ubuntu-latest
+    if: github.event.pull_request.merged == true
+
+    steps:
+      - name: Log PR Author Info
+        run: |
+          echo "PR Author Login: ${{ github.event.pull_request.user.login }}"
+          echo "PR Author ID: ${{ github.event.pull_request.user.id }}"
+          echo "PR Author Type: ${{ github.event.pull_request.user.type }}"
+          echo "PR Author Node ID: ${{ github.event.pull_request.user.node_id }}"
+
+      - name: Post Thank You Comment
+        if: >-
+          github.event.pull_request.user.login != 'aklinker1' &&
+          github.event.pull_request.user.login != 'Timeraa' &&
+          github.event.pull_request.user.login != 'PatrykKuniczak' &&
+          github.event.pull_request.user.login != 'nishu-murmu' &&
+          github.event.pull_request.user.login != 'dependabot[bot]' &&
+          github.event.pull_request.user.login != 'copilot-swe-agent[bot]'
+        uses: actions/github-script@3a2844b7e9c422d3c10d287c895573f7108da1b3 # v9.0.0
+        env:
+          comment: Thanks for helping make WXT better!
+        with:
+          script: |
+            github.rest.issues.createComment({
+              issue_number: context.issue.number,
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              body: process.env.comment
+            })

.github/workflows/pr-title.yml

@@ -0,0 +1,26 @@
+name: 🛡️ Check PR Title
+
+on:
+  pull_request:
+    types: [opened, edited]
+
+jobs:
+  lint-pr-title:
+    runs-on: ubuntu-latest
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
+        with:
+          # Only fetch the config file from the repository
+          sparse-checkout-cone-mode: false
+          sparse-checkout: .commitlintrc.yml
+
+      - name: Install dependencies
+        run: npm install --global @commitlint/config-conventional commitlint
+
+      - name: Check PR title with commitlint
+        env:
+          PR_TITLE: ${{ github.event.pull_request.title }}
+          HELP_URL: https://github.com/wxt-dev/wxt/blob/main/CONTRIBUTING.md#conventional-pr-titles
+        run: echo "$PR_TITLE" | npx commitlint --help-url $HELP_URL

.github/workflows/publish-docs.yml

@@ -1,4 +1,4 @@
-name: Publish Docs
+name: 📝 Publish Docs
 on:
   push:
     branches:
@@ -10,18 +10,38 @@ on:
         required: true
         default: latest
 
+permissions:
+  contents: read
+
 jobs:
   publish:
+    # Only run if it's the upstream repository, not forks
+    if: github.repository == 'wxt-dev/wxt'
+    name: Publish Docs
     runs-on: ubuntu-22.04
+    permissions:
+      contents: write
     steps:
-      - uses: actions/checkout@v4
-      - uses: ./.github/actions/setup
-      - uses: docker/login-action@v3
+      - name: Checkout
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
+
+      - name: Setup
+        uses: ./.github/actions/setup
+
+      - name: Login to Docker Registry
+        uses: docker/login-action@4907a6ddec9925e35a0a9e82d7399ccc52663121 # v4.1.0
         with:
           registry: https://${{ secrets.DOCKER_REGISTRY_HOSTNAME }}
           username: ${{ secrets.DOCKER_REGISTRY_USERNAME }}
           password: ${{ secrets.DOCKER_REGISTRY_PASSWORD }}
-      - run: pnpm docs:build
-      - run: docker build docs/.vitepress -t ${{ secrets.DOCKER_REGISTRY_HOSTNAME }}/wxt/docs:${{ github.event.inputs.tag || 'latest' }}
-      - run: docker push ${{ secrets.DOCKER_REGISTRY_HOSTNAME }}/wxt/docs:${{ github.event.inputs.tag || 'latest' }}
-      - run: curl -X POST -i ${{ secrets.UPDATE_DOCS_WEBHOOK }}
+
+      - name: Build docs
+        run: |
+          bun run docs:build
+          docker build docs/.vitepress -t ${{ secrets.DOCKER_REGISTRY_HOSTNAME }}/wxt/docs:${{ github.event.inputs.tag || 'latest' }}
+
+      - name: Push Image
+        run: docker push ${{ secrets.DOCKER_REGISTRY_HOSTNAME }}/wxt/docs:${{ github.event.inputs.tag || 'latest' }}
+
+      - name: Deploy
+        run: 'curl -X POST -i -H "X-API-Key: ${{ secrets.DOCS_WEBHOOK_API_KEY }}" https://${{ secrets.DOCS_WEBHOOK_DOMAIN }}/api/webhook/stacks/${{ secrets.DOCS_WEBHOOK_STACK_ID }}'

.github/workflows/release.yml

@@ -1,38 +1,105 @@
-name: Release
+name: 🚀 Release
 on:
   workflow_dispatch:
+    inputs:
+      package:
+        description: Package to release
+        default: wxt
+        type: choice
+        options:
+          - analytics
+          - auto-icons
+          - i18n
+          - is-background
+          - module-react
+          - module-solid
+          - module-svelte
+          - module-vue
+          - runner
+          - storage
+          - unocss
+          - webextension-polyfill
+          - wxt
+      bump:
+        description: Blank (auto), a version (1.4.1), or major/minor/patch
+        type: string
+      dryRun:
+        description: Do a dry-run and don't publish anything
+        type: boolean
+        default: false
+
+permissions:
+  contents: read
 
 jobs:
   validate:
+    name: Validate
     uses: './.github/workflows/validate.yml'
     secrets: inherit
+    if: ${{ inputs.dryRun != true }}
 
   publish:
-    runs-on: ubuntu-22.04
+    name: Publish ${{ case(inputs.dryRun, ' (dry-run)', '') }}
+    runs-on: ubuntu-24.04
+    permissions:
+      contents: write # Push version changes
+      id-token: write # OIDC for NPM publishing
     needs:
       - validate
+    # Allow dry runs to skip validation but still run this job
+    if: |
+      always() &&
+      (needs.validate.result == 'success' || needs.validate.result == 'skipped')
     steps:
-      - uses: actions/checkout@v4
+      - name: Checkout
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
         with:
           fetch-depth: 0
+          ssh-key: ${{ secrets.DEPLOY_KEY }} # https://github.com/sbellone/release-workflow-example
 
-      - uses: ./.github/actions/setup
+      - name: Setup
+        uses: ./.github/actions/setup
 
-      - name: Bump and Tag
+      - name: Configure Git
         run: |
-          git config user.email "github-actions@users.noreply.github.com"
-          git config user.name "GitHub Actions"
-          pnpx changelogen@latest --release
-          git push
-          git push --tags
-        working-directory: packages/wxt
+          git config user.name 'github-actions[bot]'
+          git config user.email 'github-actions[bot]@users.noreply.github.com'
 
-      - name: NPM
-        run: |
-          echo "//registry.npmjs.org/:_authToken=${{ secrets.NPM_AUTH_TOKEN }}" > ~/.npmrc
-          pnpm publish
-        working-directory: packages/wxt
+      - name: Upgrade NPM for Provence
+        run: sudo npm i -g npm@latest
 
-      - name: GitHub Release
-        run: pnpx changelogen@latest gh release --token ${{ secrets.GITHUB_TOKEN }}
-        working-directory: packages/wxt
+      - name: Bump and Release
+        uses: aklinker1/zero-changelog/actions/release@b6fcca17cebfc45f996b80fe5926da924d8441f8 # 0.2.1
+        with:
+          bump: ${{ inputs.bump }}
+          path: packages/${{ inputs.package }}
+          # Include documentation updates in WXT's releases
+          additionalDirs: |-
+            ${{ case(
+              inputs.package == 'wxt', 'docs',
+              ''
+            ) }}
+          # Use package name in commit message
+          commitTemplate: |-
+            ${{ case(
+              inputs.package == 'wxt', 'chore(release): wxt v{{version}}',
+              'chore(release): @wxt-dev/{{dirname}} v{{version}}'
+            ) }}
+          # Use package name in release name
+          releaseNameTemplate: |-
+            ${{ case(
+              inputs.package == 'wxt', 'wxt v{{version}}',
+              '@wxt-dev/{{dirname}} v{{version}}'
+            ) }}
+          # Update lockfile with new versions since it includes the package versions
+          preCommitCommands: |-
+            bun i
+          publishCommands: |-
+            bun pm pack
+            npm publish *.tgz
+          dryRun: ${{ inputs.dryRun }}
+          dryRunPublishCommands: |-
+            bun pm pack
+            npm publish *.tgz --dry-run
+          githubToken: ${{ secrets.GITHUB_TOKEN }}
+          latestRelease: ${{ inputs.package == 'wxt' }}

.github/workflows/sync-releases.yml

@@ -1,23 +0,0 @@
-name: Sync Releases
-on:
-  workflow_dispatch:
-  push:
-    branches:
-      - main
-    paths:
-      - packages/wxt/CHANGELOG.md
-
-jobs:
-  sync:
-    runs-on: ubuntu-22.04
-    steps:
-      - uses: actions/checkout@v4
-      - uses: pnpm/action-setup@v3
-        with:
-          version: 8
-      - uses: actions/setup-node@v4
-        with:
-          node-version: 18
-          cache: pnpm
-      - run: pnpm sync-releases all --token ${{ secrets.GITHUB_TOKEN }}
-        working-directory: packages/wxt

.github/workflows/update-browser-package.yml

@@ -0,0 +1,51 @@
+name: 🔄 Update @wxt-dev/browser
+on:
+  workflow_dispatch:
+  schedule:
+    - cron: '0 0 * * *' # Every day at midnight
+
+permissions:
+  contents: read
+
+jobs:
+  sync:
+    name: 'Sync with @types/chrome'
+    runs-on: ubuntu-latest
+    if: github.repository_owner == 'wxt-dev'
+    permissions:
+      contents: write # Push version changes
+      id-token: write # OIDC for NPM publishing
+    steps:
+      - name: Checkout
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
+        with:
+          ssh-key: ${{ secrets.DEPLOY_KEY }}
+
+      - name: Setup
+        uses: ./.github/actions/setup
+        with:
+          installArgs: --ignore-scripts
+
+      - name: Generate Latest Code
+        working-directory: packages/browser
+        run: bun run gen
+
+      - name: Run Checks
+        working-directory: packages/browser
+        run: bun run check
+
+      - name: Commit Changes
+        id: commit
+        uses: stefanzweifel/git-auto-commit-action@4a55954c782fc1ea30b9056cd3e7a2b40ca8887d # v7.2.0
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        with:
+          commit_message: 'fix: Upgrade `@wxt-dev/browser` to latest `@types/chrome` version'
+
+      - name: Publish to NPM
+        if: steps.commit.outputs.changes_detected == 'true'
+        working-directory: packages/browser
+        run: |
+          bun pm pack
+          sudo npm i -g npm@latest
+          npm publish *.tgz

.github/workflows/validate.yml

@@ -1,4 +1,4 @@
-name: Validate
+name: 🛡️ Validate
 on:
   workflow_call:
   pull_request:
@@ -6,42 +6,97 @@ on:
     branches:
       - main
 
+permissions:
+  contents: read
+
 jobs:
   checks:
+    name: Checks
     runs-on: ubuntu-22.04
     steps:
-      - uses: actions/checkout@v4
-      - uses: ./.github/actions/setup
-      - run: pnpm check
+      - name: Checkout
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
+
+      - name: Setup
+        uses: ./.github/actions/setup
+
+      - name: Basic Checks
+        run: bun run check
+
+  builds:
+    name: Builds
+    runs-on: ubuntu-22.04
+    steps:
+      - name: Checkout
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
+
+      - name: Setup
+        uses: ./.github/actions/setup
+
+      - name: Build All Packages
+        run: bun run buildc all
+
   build-demo:
+    name: Build Demo
     runs-on: ubuntu-22.04
     steps:
-      - uses: actions/checkout@v4
-      - uses: ./.github/actions/setup
-      - run: pnpm build:all
+      - name: Checkout
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
+
+      - name: Setup
+        uses: ./.github/actions/setup
+
+      - name: Build
+        run: bun run build:all
         working-directory: packages/wxt-demo
-      - run: pnpm wxt zip
+
+      - name: ZIP
+        run: bun run wxt zip
         working-directory: packages/wxt-demo
+
   tests:
-    runs-on: ubuntu-22.04
+    name: Tests (${{ matrix.title }})
+    runs-on: ${{ matrix.os }}
+    strategy:
+      matrix:
+        include:
+          - title: 'Linux'
+            os: ubuntu-22.04
+            coverage: true
+          - title: 'Windows'
+            os: windows-latest
+            coverage: false
     steps:
-      - uses: actions/checkout@v4
-      - uses: ./.github/actions/setup
-      - uses: oven-sh/setup-bun@v1
-      - name: pnpm test:coverage
-        run: pnpm test:coverage --reporter=default --reporter=hanging-process
-      - uses: codecov/codecov-action@v4
+      - name: Checkout
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
+
+      - name: Setup
+        uses: ./.github/actions/setup
+
+      - name: Setup PNPM
+        uses: pnpm/action-setup@0ebf47130e4866e96fce0953f49152a61190b271 # v6.0.9
+        with:
+          version: latest
+
+      - name: Run Tests
+        if: ${{ ! matrix.coverage }}
+        run: bun run test
+
+      - name: Run Tests (Coverage)
+        if: matrix.coverage
+        run: bun run test:coverage --reporter=default --reporter=hanging-process
+
+      - name: Upload Coverage
+        if: matrix.coverage
+        uses: codecov/codecov-action@fb8b3582c8e4def4969c97caa2f19720cb33a72f # v7.0.0
         env:
           CODECOV_TOKEN: ${{ secrets.CODECOV_TOKEN }}
-  windows-tests:
-    runs-on: windows-latest
-    steps:
-      - uses: actions/checkout@v4
-      - uses: ./.github/actions/setup
-      - run: pnpm test run
+
   template:
+    name: Template
     runs-on: ubuntu-22.04
     strategy:
+      fail-fast: false
       matrix:
         template:
           - react
@@ -50,19 +105,34 @@ jobs:
           - vanilla
           - vue
     steps:
-      - uses: actions/checkout@v4
-      - uses: ./.github/actions/setup
-      - run: pnpm pack
+      - name: Checkout
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
+
+      - name: Setup
+        uses: ./.github/actions/setup
+
+      - name: Pack WXT package
+        run: bun pm pack
         working-directory: packages/wxt
-      - run: npm i
+
+      - name: Install Dependencies
+        run: npm i
         working-directory: templates/${{ matrix.template }}
-      - run: npm i -D ../../packages/wxt/wxt-*.tgz
+
+      - name: Install Packed WXT
+        run: npm i -D ../../packages/wxt/wxt-*.tgz
         working-directory: templates/${{ matrix.template }}
-      - run: pnpm compile
+
+      - name: Type Check Template
+        run: bun run compile
         if: matrix.template != 'svelte'
         working-directory: templates/${{ matrix.template }}
-      - run: pnpm check
+
+      - name: Type Check Template
+        run: bun run check
         if: matrix.template == 'svelte'
         working-directory: templates/${{ matrix.template }}
-      - run: pnpm build
+
+      - name: Build Template
+        run: bun run build
         working-directory: templates/${{ matrix.template }}

.github/workflows/vhs.yml

@@ -0,0 +1,58 @@
+name: 📼 VHS
+on:
+  push:
+    paths:
+      - docs/tapes/*.tape
+      - .github/workflows/vhs.yml
+  pull_request:
+    paths:
+      - docs/tapes/*.tape
+      - .github/workflows/vhs.yml
+  workflow_dispatch:
+
+permissions:
+  contents: read
+
+jobs:
+  vhs:
+    name: Create VHS
+    runs-on: macos-latest
+    if: ${{ github.repository == 'wxt-dev/wxt' }}
+    permissions:
+      contents: write
+    steps:
+      - name: Checkout
+        uses: actions/checkout@9c091bb21b7c1c1d1991bb908d89e4e9dddfe3e0 # v7.0.0
+        with:
+          ssh-key: ${{ secrets.DEPLOY_KEY }}
+
+      - name: Setup
+        uses: ./.github/actions/setup
+
+      - name: Setup Go
+        uses: actions/setup-go@924ae3a1cded613372ab5595356fb5720e22ba16
+        with:
+          go-version: '1.25.1'
+
+      # This prevents bunx from downloading WXT in the video, and it uses the checked-out version
+      - name: Build WXT
+        working-directory: packages/wxt
+        run: bun run build
+
+      - name: Record VHS
+        run: |
+          brew install ttyd ffmpeg
+          go install github.com/charmbracelet/vhs@517bcda0faf416728bcf6b7fe489eb0e2469d9b5 # v0.10.0
+          vhs docs/tapes/init-demo.tape
+
+      - name: Save recorded GIF
+        uses: stefanzweifel/git-auto-commit-action@4a55954c782fc1ea30b9056cd3e7a2b40ca8887d # v7.2.0
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        with:
+          commit_message: 'docs: Update `wxt init` GIF'
+          commit_user_name: github-actions[bot]
+          commit_user_email: github-actions[bot]@users.noreply.github.com
+          commit_author: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
+          # https://github.com/charmbracelet/vhs#output
+          file_pattern: 'docs/assets/*.gif'

.gitignore

@@ -1,13 +1,16 @@
 .DS_Store
 .env
 .env.*
+!packages/wxt/src/core/utils/__tests__/fixtures/.env
 .idea
 .output
 .webextrc
 .wxt
+.wxt-runner
 *.log
-/.vscode/
+*.tgz
 /docs/.vitepress/cache
+docs/.vitepress/.temp
 coverage
 dist
 node_modules
@@ -17,6 +20,7 @@ web-ext.config.ts
 templates/*/pnpm-lock.yaml
 templates/*/yarn.lock
 templates/*/package-lock.json
-docs/api
+docs/api/reference
 stats.html
-.tool-versions
+.cache
+*-stats.txt

.markdownlint.json

@@ -0,0 +1,6 @@
+{
+  "$schema": "https://raw.githubusercontent.com/DavidAnson/markdownlint/refs/heads/main/schema/markdownlint-config-schema.json",
+  "line-length": false,
+  "no-inline-html": false,
+  "first-line-heading": false
+}

.markdownlintignore

@@ -0,0 +1,9 @@
+node_modules
+.git
+.output
+dist
+
+# Generated files
+packages/wxt/README.md
+packages/*/CHANGELOG.md
+docs/api

.prettierignore

@@ -5,3 +5,4 @@ dist
 docs/.vitepress/cache
 pnpm-lock.yaml
 CHANGELOG.md
+packages/browser/src/gen

.prettierrc.yml

@@ -1,2 +1,4 @@
 singleQuote: true
 endOfLine: lf
+plugins:
+  - prettier-plugin-jsdoc

.tool-versions

@@ -0,0 +1,2 @@
+bun 1.3.13
+nodejs 24.14.1

.vscode/extensions.json

@@ -0,0 +1,7 @@
+{
+  "recommendations": [
+    "davidanson.vscode-markdownlint",
+    "esbenp.prettier-vscode",
+    "github.vscode-github-actions"
+  ]
+}

.vscode/settings.json

@@ -0,0 +1,15 @@
+{
+  // Set default formatter
+  "editor.defaultFormatter": "esbenp.prettier-vscode",
+
+  "[json]": { "editor.defaultFormatter": "esbenp.prettier-vscode" },
+  "[yaml]": { "editor.defaultFormatter": "esbenp.prettier-vscode" },
+  "[typescript]": { "editor.defaultFormatter": "esbenp.prettier-vscode" },
+  "[markdown]": { "editor.defaultFormatter": "esbenp.prettier-vscode" },
+
+  // Additional guidelines for Copilot
+  "github.copilot.chat.codeGeneration.instructions": [
+    { "file": "CONTRIBUTING.md" }
+  ],
+  "oxc.enable": true
+}

CODE_OF_CONDUCT.md

@@ -0,0 +1,128 @@
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, religion, or sexual identity
+and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+- Focusing on what is best not just for us as individuals, but for the
+  overall community
+
+Examples of unacceptable behavior include:
+
+- The use of sexualized language or imagery, and sexual attention or
+  advances of any kind
+- Trolling, insulting or derogatory comments, and personal or political attacks
+- Public or private harassment
+- Publishing others' private information, such as a physical or email
+  address, without their explicit permission
+- Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement at
+<aaronklinker1@gmail.com>.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series
+of actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or
+permanent ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within
+the community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.0, available at
+<https://www.contributor-covenant.org/version/2/0/code_of_conduct.html>.
+
+Community Impact Guidelines were inspired by [Mozilla's code of conduct
+enforcement ladder](https://github.com/mozilla/diversity).
+
+[homepage]: https://www.contributor-covenant.org
+
+For answers to common questions about this code of conduct, see the FAQ at
+<https://www.contributor-covenant.org/faq>. Translations are available at
+<https://www.contributor-covenant.org/translations>.

CONTRIBUTING.md

@@ -1,29 +1,59 @@
 # Contributing
 
-Everyone is welcome to contribute to WXT!
+Everyone is welcome to contribute to **WXT**!
 
 If you are changing the docs or fixing a bug, feel free to fork and open a PR.
 
 If you want to add a new feature, please create an issue or discussion first so we can decide if the feature is inline with the vision for WXT.
 
+## WXT's Vision
+
+WXT is two things:
+
+1. A build tool
+2. A set of runtime utilities
+
+The long term goal of WXT is provide an opinionated build tool that keeps WXT projects standard, while providing light-weight runtime utils that simplify a lot of the boilerplate/overhead when setting up a new extension.
+
+I also want to provide a way for developers to use either one of those two things independently, and not require them to use both. This is why all of WXT's runtime utils are shipped as their own NPM packages, most of them not bundled inside the core `wxt` package. If you just want to use the packages, they're available, and if you just want to use WXT's built tool, you don't have to import any of WXT's utilities, you can use your own.
+
+> The few runtime utils shipped inside WXT are things that should be used by 90% of extensions. That said, they're also legacy utils left in from before I started creating separate NPM packages, and in the future, they may be removed from the core package.
+
 ## Conventional Commits
 
-This project uses [Conventional Commits](https://www.conventionalcommits.org/en) to automate versioning. If you're a new contributor, don't worry about this. When you open a PR, a maintainer will change the PR's title so it's in the style of conventional commits, but that's all.
+This project uses [Conventional Commit format](https://www.conventionalcommits.org/en/v1.0.0/) to automatically generate a changelog and better understand the changes in the project
 
-Maintainers, commits to the `main` branch (either directly or via PRs) must be valid conventional commits.
+Here are some examples of conventional commit messages:
+
+- `feat: add new functionality`
+- `fix: correct typos in code`
+- `ci: add GitHub Actions for automated testing`
+
+## Conventional PR Titles
+
+The title of your pull request should follow the [conventional commit format](#conventional-commits). When a pull request is merged to the main branch, all changes are going to be squashed into a single commit. The message of this commit will be the title of the pull request. And for every release, the commit messages are used to generate the changelog.
+
+## Breaking Changes Policy
+
+A quick word on WXT's breaking changes policy. I am willing to make breaking changes, but they have to be for a good enough reason - they have to make WXT better as a whole, they can't be based on one opinion.
+
+Breaking changes also require a major release. Major releases have happened once or twice a year, so after you merge your PR, you'll have to wait a little bit before it is released.
+
+To make a breaking change:
+
+1. Make sure you're PR is targeting the `major` branch
+2. Add `!` after the conventional commit type (`fix!: ...`, `feat!: ...`, `chore!: ...`, etc) to indicate that it is a breaking change
+3. At the top of the PR, provide documentation that will inform developers about the breaking change, why it was done, and how to migrate their extension so nothing breaks.
+   - This documentation will be put ["Upgrading WXT"](https://wxt.dev/guide/resources/upgrading.html) page in the docs, read through previous breaking change docs for an idea of what is required.
 
 ## Setup
 
-WXT uses `pnpm`, so make sure you have it installed.
+WXT uses Bun for package management and development. Install it from: <https://bun.com/>
+
+Then install dependencies:
 
 ```sh
-corepack enable
-```
-
-Then, simply run the install command:
-
-```sh
-pnpm i
+bun install
 ```
 
 ## Development
@@ -31,32 +61,68 @@ pnpm i
 Here are some helpful commands:
 
 ```sh
-# Build WXT package
-pnpm build
+# Build WXT package and workspace dependencies
+bun run --filter wxt build
 ```
 
 ```sh
-# Build WXT package, then build demo extension
-cd packages/wxt-demo
-pnpm build
-```
-
-```sh
-# Build WXT package, then start the demo extension in dev mode
-cd packages/wxt-demo
-pnpm dev
+# Build workspace dependencies, then start the demo extension in dev mode
+bun run --filter wxt-demo dev
 ```
 
 ```sh
 # Run unit and E2E tests
-pnpm test
+bun run test
 ```
 
 ```sh
 # Start the docs website locally
-pnpm docs:dev
+bun run docs:dev
 ```
 
+> Above, we used bun's `--filter` flag to choose which package to run a command in, but there are other ways:
+>
+> ```sh
+> bun run -F @wxt-dev/i18n build
+> # or
+> bun run --cwd packages/i18n build
+> # or
+> cd packages/i18n
+> bun run build
+> ```
+>
+> Pick your poison!
+
+## Profiling
+
+```sh
+# Build the latest version
+bun run --filter wxt build
+
+# CD to the demo directory
+cd packages/wxt-demo
+```
+
+Then there are a few different ways to profile WXT commands:
+
+- Generate a flamechart with 0x:
+
+  ```sh
+  bunx 0x node_modules/wxt/bin/wxt.mjs build
+  ```
+
+- Create a CPU profile:
+
+  ```sh
+  bun run --cpu-prof node_modules/wxt/bin/wxt.mjs build
+  ```
+
+- Debug the process:
+
+  ```sh
+  bun run --inspect node_modules/wxt/bin/wxt.mjs build
+  ```
+
 ## Updating Docs
 
 Documentation is written with VitePress, and is located in the `docs/` directory.
@@ -72,7 +138,7 @@ WXT has unit and E2E tests. When making a change or adding a feature, make sure
 To run tests for a specific file, add the filename at the end of the test command:
 
 ```sh
-pnpm test manifest-contents
+bun run --filter wxt test manifest-contents
 ```
 
 All test (unit and E2E) for all packages are ran together via [Vitest workspaces](https://vitest.dev/guide/#workspaces-support).
@@ -81,7 +147,7 @@ If you want to manually test a change, you can modify the demo project for your
 
 ## Templates
 
-Each directory inside `templates/` is it's own standalone project. Simply `cd` into the directory you're updating, install dependencies with `npm` (NOT `pnpm`), and run the relevant commands
+Each directory inside `templates/` is it's own standalone project. Simply `cd` into the directory you're updating, install dependencies with `npm` (NOT `bun`), and run the relevant commands
 
 ```sh
 cd templates/vue
@@ -97,7 +163,7 @@ Note that templates are hardcoded to a specific version of `wxt` from NPM, they
     "typescript": "^5.3.2",
     "vite-plugin-solid": "^2.7.0",
 -   "wxt": "^0.8.0"
-+   "wxt": "../.."
++   "wxt": "../../packages/wxt"
   }
 ```
 
@@ -112,3 +178,61 @@ cp -r templates/vanilla templates/<new-template-name>
 ```
 
 That's it. Once your template is merged, it will be available inside `wxt init` immediately. You don't need to release a new version of WXT to release a new template.
+
+## Releasing Updates
+
+Releases are done with GitHub actions:
+
+- Use the [Release workflow](https://github.com/wxt-dev/wxt/actions/workflows/release.yml) to release a single package in the monorepo. This automatically detects the version change with conventional commits, builds and uploads the package to NPM, and creates a GitHub release.
+- Use the [Sync Releases workflow](https://github.com/wxt-dev/wxt/actions/workflows/sync-releases.yml) to sync the GitHub releases with changes to the changelog. To change a release, update the `CHANGELOG.md` file and run the workflow. It will sync the releases of a single package in the monorepo.
+
+## Upgrading Dependencies
+
+WXT has custom rules around what dependencies can be upgraded. Use the `scripts/upgrade-deps.ts` script to upgrade dependencies and follow these rules.
+
+```sh
+bun run scripts/upgrade-deps.ts
+```
+
+To see all the options, run:
+
+```sh
+bun run scripts/upgrade-deps.ts --help
+```
+
+## Install Unreleased Versions
+
+This repo uses <https://pkg.pr.new> to publish versions of all it's packages for almost every commit. You can install them via:
+
+```sh
+npm i https://pkg.pr.new/[package-name]@[ref]
+```
+
+Or use one of the shorthands:
+
+```sh
+# Install the latest build of `wxt` from a PR:
+npm i https://pkg.pr.new/wxt@1283
+
+# Install the latest build of `@wxt-dev/module-react` on the `main` branch
+npm i https://pkg.pr.new/@wxt-dev/module-react@main
+
+# Install `@wxt-dev/storage` from a specific commit:
+npm i https://pkg.pr.new/@wxt-dev/module-react@426f907
+```
+
+## Blog Posts
+
+Anyone is welcome to submit a blog post on <https://wxt.dev/blog>!
+
+> [!NOTE]
+> Before starting on a blog post, please message Aaron on Discord or start a discussion on GitHub to get permission to write about a topic, but most topics are welcome: Major version updates, tutorials, etc.
+
+- **English only**: Blog posts should be written in English. Unfortunately, our maintainers don't have the bandwidth right now to translate our docs, let alone blog posts. Sorry 😓
+- **AI**: Please only use AI to translate or proof-read your blog post. Don't generate the whole thing... We don't want to publish that.
+
+## Become a Maintainer
+
+If you're interested in becoming a maintainer, send an email to Aaron at <aaronklinker1@gmail.com> with your github username saying you're interested. The process is very informal, I will add you quickly if you've contributed code or answered questions and helped out the community!
+
+Maintainers don't have to just write code - they can manage issues, answer questions, review PRs, organize and prioritize work - there's lots of ways for you to help out.

MAINTAINERS.md

@@ -0,0 +1,90 @@
+# Maintainers
+
+A couple of things for you to consider before merging a PR or giving the go-ahead on a feature proposal.
+
+## Be picky about new features and packages
+
+We are responsible for maintaining them and fixing related bugs after the PR is merged. The community can always release their own WXT modules or packages, not everything needs to be built into WXT.
+
+## Prefer standards over customization
+
+Don't merge PRs that just add another way to do something, like [this one](https://github.com/wxt-dev/wxt/pull/2053#issuecomment-3857010196).
+
+WXT is opinionated, if you have questions about what is WXT's opinion or we need to create a new one, create an issue and @ me to discuss.
+
+## PRs should be small and targeted
+
+A PR should make one change. They should not make any unrelated changes outside of accomplishing the one thing. This makes PRs easier to review and they get merged more quickly - a win-win for everyone.
+
+## `@wxt-dev/*` packages are separate
+
+We can't make changes to these packages assuming people are using them only with WXT. For example, I almost missed [this PR](https://github.com/wxt-dev/wxt/pull/2049#issuecomment-3861251599).
+
+I want these packages to be usable on their own so if people don't like WXT's build tool, they can still use our other awesome packages.
+
+## Minimize dependencies
+
+I don't like how heavy lots of frameworks are. It's unavoidable to a certain extent, but if you can do something without another dependency, try to.
+
+If you need a dependency, look for one with zero dependencies and that's respectable.
+
+## Look at milestones
+
+I've organized WXT's long term plans into [milestones](https://github.com/wxt-dev/wxt/milestones), check those out to get an idea of my priorities for some of the larger features.
+
+## Require tests
+
+If someone opens a PR to fix a bug but doesn't include tests, don't merge the PR. Tests are required to prevent regressions and maintain a codebase long term.
+
+## Ask for reproductions for bugs
+
+You don't need to triage bugs if someone doesn't give you enough information. You can always ask for a repo with a reproduction or wait for more details.
+
+If there's not an easy way to reproduce a bug, you're wasting your time triaging it. Just be mindful of your own time!
+
+Here's an example of how to ask for a reproduction: <https://github.com/wxt-dev/wxt/issues/2064#issuecomment-3862579110>. You could be more blunt than this.
+
+## Add yourself as a code owner
+
+If you want to be responsible for a specific package or directory, add yourself to the [`.github/CODEOWNERS`](https://github.com/wxt-dev/wxt/blob/main/.github/CODEOWNERS) file to get added as a reviewer to PRs automatically. You can also add yourself to the default list to be added as a reviewer on all PRs.
+
+## Releasing Package Updates
+
+Releases are done with GitHub actions:
+
+- Use the [Release workflow](https://github.com/wxt-dev/wxt/actions/workflows/release.yml) to release a single package in the monorepo. This automatically detects the version change with conventional commits, builds and uploads the package to NPM, and creates a GitHub release.
+- Use the [Sync Releases workflow](https://github.com/wxt-dev/wxt/actions/workflows/sync-releases.yml) to sync the GitHub releases with changes to the changelog. To change a release, update the `CHANGELOG.md` file and run the workflow. It will sync the releases of a single package in the monorepo.
+
+## Creating New Packages
+
+Example PR: <https://github.com/wxt-dev/wxt/pull/2152>
+
+1. Create the package.
+
+2. Update CI workflow inputs.
+
+3. Add docs page and version for "Other Packages" dropdown.
+
+4. Merge the PR.
+
+5. Tag the commit (look at other tags for pattern):
+
+   ```sh
+   git tag <dir-name>-v<version>
+   git push --tags
+   ```
+
+6. Publish the package to NPM:
+
+   ```sh
+   cd packages/<dir-name>
+   bun publish --access public
+   ```
+
+7. Create a basic release on GitHub mentioning the new package is available.
+
+A couple of things to note:
+
+- pkg.pr.new will fail on the original PR. It's fine to ignore and merge your PR as long as it fails due to your new package not being published to NPM yet.
+- The regular release workflow DOES NOT WORK for new packages. You have to have at least one `<dir-name>-v<version>` tag created before you can run that workflow for your new package.
+- You don't need to create a CHANGELOG.md file for the package, it will be created automatically after future changes are released via the normal release workflow.

README.md

@@ -1,50 +1,41 @@
-<h1 align="center">
-  <img style="vertical-align:middle" width="44" src="./docs/public/hero-logo.svg" alt="WXT Logo">
-  <span>WXT</span>
-</h1>
+<div align="center">
 
-<p align="center">
-  <a href="https://www.npmjs.com/package/wxt" target="_blank"><img alt="npm" src="https://img.shields.io/npm/v/wxt?labelColor=black&color=%234fa048"></a>
-  <span> </span>
-  <a href="https://www.npmjs.com/package/wxt" target="_blank"><img alt="npm" src="https://img.shields.io/npm/dm/wxt?labelColor=black&color=%234fa048"></a>
-  <span> </span>
-  <a href="https://github.com/wxt-dev/wxt/blob/main/LICENSE" target="_blank"><img alt="NPM" src="https://img.shields.io/npm/l/wxt?labelColor=black&color=%234fa048"></a>
-  <span> </span>
-  <a href="https://codecov.io/github/wxt-dev/wxt" target="_blank"><img alt="Codecov" src="https://img.shields.io/codecov/c/github/wxt-dev/wxt?labelColor=black&color=%234fa048"></a>
-</p>
+# <img align="top" width="44" src="https://raw.githubusercontent.com/wxt-dev/wxt/HEAD/docs/public/hero-logo.svg" alt="WXT Logo"> WXT
 
-<p align="center">
-  <span>Next-gen framework for developing web extensions.</span>
-  <br/>
-  <span>⚡</span>
-  <br/>
-  <q><i>It's like Nuxt, but for Chrome Extensions</i></q>
-</p>
+[![npm version](https://img.shields.io/npm/v/wxt?labelColor=black&color=%234fa048)](https://www.npmjs.com/package/wxt)
+[![downloads](https://img.shields.io/npm/dm/wxt?labelColor=black&color=%234fa048)](https://www.npmjs.com/package/wxt)
+[![license | MIT](https://img.shields.io/npm/l/wxt?labelColor=black&color=%234fa048)](https://github.com/wxt-dev/wxt/blob/main/LICENSE)
+[![coverage](https://img.shields.io/codecov/c/github/wxt-dev/wxt?labelColor=black&color=%234fa048)](https://codecov.io/github/wxt-dev/wxt)
 
-<p align="center">
-  <a href="https://wxt.dev" target="_blank">Get Started</a>
-  &bull;
-  <a href="https://wxt.dev/guide/installation.html" target="_blank">Installation</a>
-  &bull;
-  <a href="https://wxt.dev/api/config.html" target="_blank">Configuration</a>
-  &bull;
-  <a href="https://wxt.dev/examples.html" target="_blank">Examples</a>
-  &bull;
-  <a href="https://discord.gg/ZFsZqGery9" target="_blank">Discord</a>
-</p>
+Next-gen framework for developing web extensions.<br/>⚡<br/><q><i>It's like Nuxt, but for Web Extensions</i></q>
 
-![Example CLI Output](./docs/assets/cli-output.png)
+[Get Started](https://wxt.dev/guide/installation.html) •
+[Configuration](https://wxt.dev/api/config.html) •
+[Examples](https://wxt.dev/examples.html) •
+[Changelog](https://github.com/wxt-dev/wxt/blob/main/packages/wxt/CHANGELOG.md) •
+[Discord](https://discord.gg/ZFsZqGery9)
+
+</div>
+
+![Example CLI Output](https://raw.githubusercontent.com/wxt-dev/wxt/HEAD/docs/assets/cli-output.png)
 
 ## Demo
 
-https://github.com/wxt-dev/wxt/assets/10101283/4d678939-1bdb-495c-9c36-3aa281d84c94
+<https://github.com/wxt-dev/wxt/assets/10101283/4d678939-1bdb-495c-9c36-3aa281d84c94>
 
 ## Quick Start
 
 Bootstrap a new project:
 
 ```sh
-pnpm dlx wxt@latest init <project-name>
+# npm
+npx wxt@latest init
+
+# pnpm
+pnpm dlx wxt@latest init
+
+# bun
+bunx wxt@latest init
 ```
 
 Or see the [installation guide](https://wxt.dev/guide/installation.html) to get started with WXT.
@@ -59,12 +50,19 @@ Or see the [installation guide](https://wxt.dev/guide/installation.html) to get
 - 🦾 Auto-imports
 - 🤖 Automated publishing
 - 🎨 Frontend framework agnostic: works with Vue, React, Svelte, etc
+- 📦 [Module system](https://wxt.dev/guide/essentials/wxt-modules.html#overview) for reusing code between extensions
 - 🖍️ Quickly bootstrap a new project
 - 📏 Bundle analysis
-- ⬇️ Download and bundle remote URL imports
+
+## Sponsors
+
+WXT is a [MIT-licensed](https://github.com/wxt-dev/wxt/blob/main/LICENSE) open source project with its ongoing development made possible entirely by the support of these awesome backers. If you'd like to join them, please consider [sponsoring WXT's development](https://github.com/sponsors/wxt-dev).
+
+[![WXT Sponsors](https://raw.githubusercontent.com/wxt-dev/static/refs/heads/main/sponsorkit/sponsors.svg)](https://github.com/sponsors/wxt-dev)
 
 ## Contributors
 
-<a href="https://github.com/wxt-dev/wxt/graphs/contributors">
-  <img src="https://contrib.rocks/image?repo=wxt-dev/wxt" />
-</a>
+Published under the [MIT](https://github.com/wxt-dev/wxt/blob/main/LICENSE) license.
+Made by [@aklinker1](https://github.com/aklinker1) and [community](https://github.com/wxt-dev/wxt/graphs/contributors) 💛
+
+[![WXT contributors](https://contrib.rocks/image?repo=wxt-dev/wxt)](https://github.com/wxt-dev/wxt/graphs/contributors)

SECURITY.md

@@ -0,0 +1,11 @@
+# Security Policy
+
+While WXT is in prerelease, only the latest version will receive security updates. The latest version is:
+
+<img alt="npm version" src="https://img.shields.io/npm/v/wxt?labelColor=black&color=%234fa048">
+
+## Reporting a Vulnerability
+
+If you discover a security vulnerability, please email me at <aaronklinker1@gmail.com>. I will respond within a few days to acknowledge receipt of your report.
+
+If the vulnerability is accepted, I will open a public issue to track the fix. If the vulnerability is not accepted, no further action will be taken.

cspell.yml

@@ -0,0 +1,126 @@
+version: '0.2'
+ignorePaths:
+  - pnpm-lock.yaml
+  - '**/node_modules/**'
+  - '**/dist/**'
+  - '**/coverage/**'
+  - docs/api/**
+  - '**/CHANGELOG.md'
+  - docs/public/_redirects
+  - packages/browser/src/gen/**
+  - patches/**
+  - '**/*.snap'
+  - docs/assets/extension-showcase.yml
+  - packages/*/stats.html
+words:
+  - Aabid
+  - aabidk
+  - aklinker
+  - automount
+  - avenir
+  - bidi
+  - blocklists
+  - buildc
+  - bunx
+  - cachable
+  - cacjs
+  - charmbracelet
+  - chromedriver
+  - Cira
+  - comctx
+  - confbox
+  - configfile
+  - consola
+  - consolas
+  - Cpath
+  - crbug
+  - cros
+  - crunchyroll
+  - cssinjs
+  - CSUI
+  - Csvg
+  - defu
+  - deinit
+  - dequal
+  - dtrace
+  - duckduckgo
+  - esbuild
+  - esque
+  - extglob
+  - favicons
+  - fieldtrials
+  - firefoxdeveloperedition
+  - flamechart
+  - Florian
+  - focusring
+  - frontmatter
+  - giget
+  - grayscale
+  - greyscale
+  - gtag
+  - hckhakegfgenefhikdcfkaaonnclljmf
+  - hookable
+  - iconify
+  - jsons
+  - Kenobi
+  - keystyle
+  - klinker
+  - linkedom
+  - llms
+  - locationchange
+  - magicast
+  - Menlo
+  - menupanel
+  - metas
+  - moderok
+  - mktemp
+  - mycompany
+  - nacl
+  - nanospinner
+  - natsu
+  - newtab
+  - njsproj
+  - nodebuffer
+  - Noto
+  - ntvs
+  - nypm
+  - obug
+  - ohash
+  - oklab
+  - oxlint
+  - pbbf
+  - personaltoolbar
+  - portaling
+  - posthog
+  - prebundled
+  - prefs
+  - proxified
+  - pWXLO
+  - repost
+  - rxliuli
+  - sandboxed
+  - scule
+  - Segoe
+  - sidepanel
+  - sidepanels
+  - solidjs
+  - styl
+  - subdependency
+  - tabstrip
+  - teleporting
+  - treemap
+  - triaging
+  - umami
+  - ungh
+  - unimport
+  - unocss
+  - unrun
+  - unstub
+  - unwatch
+  - USSS
+  - vitepress
+  - webext
+  - webextension
+  - webextrc
+  - xcrun
+  - xlink

docs/.vitepress/components/BlogHome.vue

@@ -0,0 +1,65 @@
+<script lang="ts" setup>
+import { computed } from 'vue';
+// @ts-expect-error: Vitepress data-loader magic, this import is correct
+import { data } from '../loaders/blog.data';
+import BlogPostPreview from './BlogPostPreview.vue';
+import { Post } from '../utils/types';
+
+const posts = computed<Post[]>(() =>
+  data
+    .map((post) => ({
+      ...post,
+      ...post.frontmatter,
+      date: new Date(post.frontmatter.date),
+    }))
+    .sort((a, b) => b.date.getTime() - a.date.getTime()),
+);
+</script>
+
+<template>
+  <div class="container">
+    <div class="inner-container">
+      <h1>Blog</h1>
+
+      <ul>
+        <BlogPostPreview v-for="post of posts" :key="post.url" :post />
+      </ul>
+    </div>
+  </div>
+</template>
+
+<style scoped>
+.container {
+  display: flex;
+  flex-direction: column;
+  align-items: center;
+
+  .inner-container {
+    padding: 32px;
+    max-width: 900px;
+    width: 100%;
+
+    h1 {
+      font-size: 32px;
+      font-weight: 600;
+      margin-top: 10px;
+      padding-bottom: 16px;
+    }
+
+    ul {
+      display: flex;
+      flex-direction: column;
+
+      li {
+        padding-top: 16px;
+        margin-top: 16px;
+
+        &:last-child {
+          padding-bottom: 16px;
+          margin-bottom: 16px;
+        }
+      }
+    }
+  }
+}
+</style>

docs/.vitepress/components/BlogLayout.vue

@@ -0,0 +1,79 @@
+<script lang="ts" setup>
+import { Ref } from 'vue';
+import useBlogDate from '../composables/useBlogDate';
+import { Content, useData } from 'vitepress';
+import { PostFrontmatter } from '../utils/types';
+
+const { frontmatter } = useData() as unknown as {
+  frontmatter: Ref<PostFrontmatter>;
+};
+
+const date = useBlogDate(() => frontmatter.value.date);
+</script>
+
+<template>
+  <div class="vp-doc">
+    <main class="container">
+      <h1 v-html="frontmatter.title" />
+      <p class="meta-row">
+        <a
+          v-for="author of frontmatter.authors"
+          :key="author.github"
+          :href="`https://github.com/${author.github}`"
+          class="author"
+        >
+          <img
+            :src="`https://github.com/${author.github}.png?size=96`"
+            alt="Author's avatar"
+          />
+          <span>{{ author.name }}</span>
+        </a>
+        <span>&bull;</span>
+        <span>{{ date }}</span>
+      </p>
+      <Content />
+    </main>
+  </div>
+</template>
+
+<style scoped>
+.vp-doc {
+  display: flex;
+
+  .container {
+    max-width: 1080px;
+    padding: 32px;
+    margin: auto;
+
+    @media (min-width: 768px) {
+      padding: 64px;
+    }
+  }
+
+  .meta-row {
+    display: flex;
+    color: var(--vp-c-text-2);
+    gap: 16px;
+    overflow: hidden;
+    padding-bottom: 32px;
+
+    .author {
+      display: flex;
+      gap: 8px;
+      align-items: center;
+      color: var(--vp-c-text-2);
+      font-weight: normal;
+      text-decoration: none;
+
+      :hover {
+        text-decoration: underline;
+      }
+
+      img {
+        width: 24px;
+        border-radius: 100%;
+      }
+    }
+  }
+}
+</style>

docs/.vitepress/components/BlogPostPreview.vue

@@ -0,0 +1,53 @@
+<script lang="ts" setup>
+import useBlogDate from '../composables/useBlogDate';
+
+const props = defineProps<{
+  post: {
+    title: string;
+    description?: string;
+    date: Date;
+    url: string;
+    authors: Array<{ name: string; github: string }>;
+  };
+}>();
+
+const date = useBlogDate(() => props.post.date);
+</script>
+
+<template>
+  <li class="blog-list-item">
+    <a :href="post.url">
+      <div class="vp-doc">
+        <h3 class="title" v-html="post.title" />
+        <p class="description" v-html="post.description" />
+        <p class="meta">
+          {{ post.authors.map((author) => author.name).join(', ') }}
+          &bull;
+          {{ date }}
+        </p>
+      </div>
+    </a>
+  </li>
+</template>
+
+<style scoped>
+.vp-doc {
+  * {
+    margin-block: 10px;
+  }
+
+  .title {
+    color: var(--vp-c-text-1);
+  }
+
+  .description {
+    color: var(--vp-c-text-2);
+  }
+
+  .meta {
+    font-weight: 400;
+    font-size: 12px;
+    color: var(--vp-c-text-2);
+  }
+}
+</style>

docs/.vitepress/components/EntrypointPatterns.vue

@@ -1,40 +1,65 @@
 <script lang="ts" setup>
-const props = defineProps<{
+defineProps<{
   patterns: Array<[intput: string, output: string]>;
 }>();
 </script>
 
 <template>
-  <table class="no-vertical-dividers">
+  <table class="no-vertical-dividers entrypoint-patterns">
     <thead>
       <tr>
-        <th>Input Pattern</th>
+        <th class="col-filename">Filename</th>
         <th></th>
         <th>Output Path</th>
       </tr>
     </thead>
     <tbody>
-      <tr v-for="pattern of patterns">
-        <td style="white-space: nowrap">
+      <tr v-for="pattern of patterns" :key="pattern[0]">
+        <td class="cell-input">
           <code>entrypoints/{{ pattern[0] }}</code>
         </td>
-        <td style="padding: 6px; opacity: 50%">
+        <td class="cell-arrow">
           <svg
-            xmlns="http://www.w3.org/2000/svg"
-            width="20"
             height="20"
             viewBox="0 0 24 24"
+            width="20"
+            xmlns="http://www.w3.org/2000/svg"
           >
             <path
-              fill="currentColor"
               d="M4 11v2h12l-5.5 5.5l1.42 1.42L19.84 12l-7.92-7.92L10.5 5.5L16 11H4Z"
+              fill="currentColor"
             />
           </svg>
         </td>
-        <td style="white-space: nowrap">
+        <td class="cell-output">
           <code>/{{ pattern[1] }}</code>
         </td>
       </tr>
     </tbody>
   </table>
 </template>
+
+<style scoped>
+.entrypoint-patterns {
+  width: 100%;
+
+  .col-filename {
+    width: 100%;
+  }
+
+  .cell-input {
+    white-space: nowrap;
+    padding-right: 8px;
+  }
+
+  .cell-arrow {
+    padding: 6px;
+    opacity: 0.5;
+  }
+
+  .cell-output {
+    white-space: nowrap;
+    padding-left: 8px;
+  }
+}
+</style>

docs/.vitepress/components/ExampleList.vue

@@ -1,34 +0,0 @@
-<script lang="ts" setup>
-import { ref, onMounted, computed } from 'vue';
-
-const props = defineProps<{
-  tag?: string;
-}>();
-
-const examples = ref();
-onMounted(async () => {
-  const res = await fetch(
-    'https://raw.githubusercontent.com/wxt-dev/wxt-examples/main/examples.json',
-  );
-  examples.value = await res.json();
-});
-
-const filteredExamples = computed(() => {
-  if (props.tag == null) return examples.value;
-
-  return examples.value.filter((example) => {
-    return example.tags?.includes(props.tag);
-  });
-});
-</script>
-
-<template>
-  <ul>
-    <li v-if="examples == null">Loading...</li>
-    <template v-else>
-      <li v-for="example of filteredExamples">
-        <a :href="example.url" target="_blank">{{ example.name }}</a>
-      </li>
-    </template>
-  </ul>
-</template>

docs/.vitepress/components/ExampleSearch.vue

@@ -0,0 +1,168 @@
+<script lang="ts" setup>
+import { computed, onMounted, ref, Ref, toRaw } from 'vue';
+import ExampleSearchFilterByItem from './ExampleSearchFilterByItem.vue';
+import ExampleSearchResult from './ExampleSearchResult.vue';
+import { ExamplesMetadata, KeySelectedObject } from '../utils/types';
+
+defineProps<{
+  tag?: string;
+}>();
+
+const exampleMetadata = ref<ExamplesMetadata>({
+  allApis: [],
+  allPackages: [],
+  allPermissions: [],
+  examples: [],
+});
+onMounted(async () => {
+  const res = await fetch(
+    'https://raw.githubusercontent.com/wxt-dev/examples/main/metadata.json',
+  );
+  exampleMetadata.value = await res.json();
+});
+
+const searchText = ref('');
+const selectedApis = ref<KeySelectedObject>({});
+const selectedPermissions = ref<KeySelectedObject>({});
+const selectedPackages = ref<KeySelectedObject>({});
+
+function useRequiredItems(selectedItems: Ref<KeySelectedObject>) {
+  return computed(() =>
+    Array.from(
+      Object.entries(toRaw(selectedItems.value)).reduce(
+        (set, [pkg, checked]) => {
+          if (checked) set.add(pkg);
+          return set;
+        },
+        new Set<string>(),
+      ),
+    ),
+  );
+}
+const requiredApis = useRequiredItems(selectedApis);
+const requiredPermissions = useRequiredItems(selectedPermissions);
+const requiredPackages = useRequiredItems(selectedPackages);
+
+function doesExampleMatchSelected(
+  exampleItems: string[],
+  requiredItems: Ref<string[]>,
+) {
+  const exampleItemsSet = new Set(exampleItems);
+  return !requiredItems.value.find((item) => !exampleItemsSet.has(item));
+}
+
+const filteredExamples = computed(() => {
+  const text = searchText.value.toLowerCase();
+  return exampleMetadata.value?.examples.filter((example) => {
+    const matchesText = example.searchText.toLowerCase().includes(text);
+    const matchesApis = doesExampleMatchSelected(example.apis, requiredApis);
+    const matchesPermissions = doesExampleMatchSelected(
+      example.permissions,
+      requiredPermissions,
+    );
+    const matchesPackages = doesExampleMatchSelected(
+      example.packages,
+      requiredPackages,
+    );
+    return matchesText && matchesApis && matchesPermissions && matchesPackages;
+  });
+});
+</script>
+
+<template>
+  <div class="example-layout">
+    <div class="search">
+      <input v-model="searchText" placeholder="Search for an example..." />
+    </div>
+
+    <div class="filters">
+      <ExampleSearchFilterByItem
+        v-model="selectedApis"
+        :items="exampleMetadata?.allApis"
+        label="APIs"
+      />
+      <ExampleSearchFilterByItem
+        v-model="selectedPermissions"
+        :items="exampleMetadata?.allPermissions"
+        label="Permissions"
+      />
+      <ExampleSearchFilterByItem
+        v-model="selectedPackages"
+        :items="exampleMetadata?.allPackages"
+        label="Packages"
+      />
+    </div>
+
+    <div class="results">
+      <p v-if="exampleMetadata == null">Loading examples...</p>
+      <template v-else>
+        <ul class="search-results">
+          <ExampleSearchResult
+            v-for="example of filteredExamples"
+            :key="example.name"
+            :example
+          />
+        </ul>
+        <p v-if="filteredExamples.length === 0">No matching examples</p>
+      </template>
+    </div>
+  </div>
+</template>
+
+<style scoped>
+.example-layout {
+  display: grid;
+  grid-template-areas:
+    'filters search'
+    'filters results';
+  gap: 16px;
+
+  @media only screen and (min-width: 710px) {
+    grid-template-columns: 256px 1fr;
+    grid-template-rows: auto 1fr;
+  }
+
+  .search {
+    grid-area: search;
+    background: var(--vp-c-bg-soft);
+    padding: 20px;
+    border-radius: 16px;
+
+    input {
+      font-size: 16px;
+    }
+  }
+
+  .filters {
+    grid-area: filters;
+    display: flex;
+    flex-direction: column;
+    gap: 10px;
+
+    @media only screen and (min-width: 710px) {
+      border-radius: 16px;
+    }
+  }
+
+  .results {
+    grid-area: results;
+
+    .search-results {
+      display: grid;
+      gap: 16px;
+
+      @media only screen and (min-width: 800px) {
+        grid-template-columns: repeat(2, 1fr);
+      }
+
+      @media only screen and (min-width: 1024px) {
+        grid-template-columns: repeat(3, 1fr);
+      }
+
+      a {
+        background-color: red;
+      }
+    }
+  }
+}
+</style>

docs/.vitepress/components/ExampleSearchFilterByItem.vue

@@ -0,0 +1,95 @@
+<script lang="ts" setup>
+import { computed, toRaw } from 'vue';
+import { KeySelectedObject } from '../utils/types';
+
+defineProps<{
+  label: string;
+  items?: string[];
+}>();
+
+const selectedItems = defineModel<KeySelectedObject>({
+  required: true,
+});
+
+const count = computed(() => {
+  return Object.values(toRaw(selectedItems.value)).filter(Boolean).length;
+});
+
+function toggleItem(pkg: string) {
+  selectedItems.value = {
+    ...toRaw(selectedItems.value),
+    [pkg]: !selectedItems.value[pkg],
+  };
+}
+</script>
+
+<template>
+  <div class="filter-container">
+    <p class="header">
+      <span>Filter by {{ label }}</span> <span v-if="count">({{ count }})</span>
+    </p>
+    <div class="scroll-container">
+      <ul class="items">
+        <li v-for="item in items">
+          <label :title="item" class="item-label">
+            <input
+              :checked="selectedItems[item]"
+              type="checkbox"
+              @input="toggleItem(item)"
+            />
+            <span>{{ item }}</span>
+          </label>
+        </li>
+      </ul>
+    </div>
+  </div>
+</template>
+
+<style scoped>
+.filter-container {
+  height: 300px;
+  display: flex;
+  flex-direction: column;
+  background: var(--vp-c-bg-soft);
+  border-radius: 20px;
+  scrollbar-width: thin;
+  scrollbar-color: var(--vp-c-brand-3) transparent;
+  padding-bottom: 10px;
+
+  .header {
+    padding: 8px 16px;
+    font-size: 12px;
+    font-weight: bold;
+    opacity: 50%;
+  }
+
+  .scroll-container {
+    flex: 1;
+    position: relative;
+
+    .items {
+      position: absolute;
+      overflow-y: auto;
+      inset: 0;
+      display: flex;
+      flex-direction: column;
+      gap: 4px;
+      font-size: small;
+      padding: 8px 16px 16px;
+
+      .item-label {
+        display: flex;
+        align-items: center;
+        gap: 6px;
+        cursor: pointer;
+
+        input[type='checkbox'] {
+          width: 16px;
+          height: 16px;
+          flex-shrink: 0;
+        }
+      }
+    }
+  }
+}
+</style>

docs/.vitepress/components/ExampleSearchResult.vue

@@ -0,0 +1,61 @@
+<script lang="ts" setup>
+import { Example } from '../utils/types';
+
+defineProps<{
+  example: Example;
+}>();
+</script>
+
+<template>
+  <li>
+    <a :href="example.url" target="_blank">
+      <p class="name">{{ example.name }}</p>
+      <p class="description">{{ example.description }}</p>
+      <p class="link">Open &rarr;</p>
+    </a>
+  </li>
+</template>
+
+<style scoped>
+a {
+  padding: 16px;
+  display: flex;
+  flex-direction: column;
+  border: 2px solid var(--vp-c-bg-soft);
+  border-radius: 16px;
+  gap: 8px;
+
+  &:hover {
+    outline: 2px solid var(--vp-c-brand-2);
+
+    .link {
+      opacity: 100%;
+    }
+  }
+
+  .name {
+    font-weight: 500;
+    text-overflow: ellipsis;
+    overflow: hidden;
+    white-space: nowrap;
+  }
+
+  .description {
+    opacity: 70%;
+    font-size: 14px;
+    line-height: 130%;
+    display: -webkit-box;
+    -webkit-line-clamp: 3;
+    -webkit-box-orient: vertical;
+    overflow: hidden;
+  }
+
+  .link {
+    opacity: 0;
+    transition: 250ms;
+    color: var(--vp-c-brand-2);
+    font-weight: bold;
+    text-align: right;
+  }
+}
+</style>

docs/.vitepress/components/UsingWxtSection.vue

@@ -1,142 +1,188 @@
 <script lang="ts" setup>
 import { computed } from 'vue';
-import useListExtensionDetails, {
-  ChromeExtension,
-} from '../composables/useListExtensionDetails';
+import useListExtensionDetails from '../composables/useListExtensionDetails';
+import _extensionEntries from '../../assets/extension-showcase.yml';
 
-// Add extension IDs here. Order doesn't matter, will be sorted by weekly active users
-// During the transition from chrome.google.com/webstore to
-// chromewebstore.google.com, queue.wxt.dev might return null for your
-// extension. If it does, use "<slug>/<id>" instead of just the ID. The slug
-// can be retrieved from the URL of the item on chromewebstore.google.com
-const chromeExtensionIds = [
-  'ocfdgncpifmegplaglcnglhioflaimkd', // GitHub: Better Line Counts
-  'mgmdkjcljneegjfajchedjpdhbadklcf', // Anime Skip Player
-  'bfbnagnphiehemkdgmmficmjfddgfhpl', // UltraWideo
-  'elfaihghhjjoknimpccccmkioofjjfkf', // StayFree - Website Blocker & Web Analytics
-  'okifoaikfmpfcamplcfjkpdnhfodpkil', // Doozy: Ai Made Easy
-  'lknmjhcajhfbbglglccadlfdjbaiifig', // tl;dv - Record, Transcribe & ChatGPT for Google Meet
-  'youtube中文配音/oglffgiaiekgeicdgkdlnlkhliajdlja', // Youtube中文配音
-  'agjnjboanicjcpenljmaaigopkgdnihi', // PreMiD
-  'aiakblgmlabokilgljkglggnpflljdgp', // Markdown Sticky Notes
-  'nomnkbngkijpffepcgbbofhcnafpkiep', // DocVersionRedirector
-  'ceicccfeikoipigeghddpocceifjelph', // Plex Skipper
-  'aelkipgppclpfimeamgmlonimflbhlgf', // GitHub Custom Notifier
-  'djnlaiohfaaifbibleebjggkghlmcpcj', // Fluent Read
-  'nhclljcpfmmaiojbhhnkpjcfmacfcian', // Facebook Video Controls
-  'mblkhbaakhbhiimkbcnmeciblfhmafna', // ElemSnap - Quick capture of webpage elements and conversion to images,
-  'oajalfneblkfiejoadecnmodfpnaeblh', // MS Edge TTS (Text to Speech)
-  'nedcanggplmbbgmlpcjiafgjcpdimpea', // YTBlock - Block any content from YouTube™
+interface StoreLink {
+  label: string;
+  url: string;
+}
+
+interface ListedExtension {
+  id: string;
+  name: string;
+  iconUrl: string;
+  shortDescription: string;
+  users: number;
+  rating: number | undefined;
+  stores: StoreLink[];
+}
+
+const extensionEntries = _extensionEntries as Array<{
+  chromeId?: string;
+  firefoxSlug?: string;
+  edgeId?: string;
+}>;
+
+const chromeIds = extensionEntries.flatMap((e) =>
+  e.chromeId ? [e.chromeId] : [],
+);
+const firefoxSlugs = [
+  ...new Set(
+    extensionEntries.flatMap((e) => (e.firefoxSlug ? [e.firefoxSlug] : [])),
+  ),
 ];
+const edgeIds = extensionEntries.flatMap((e) => (e.edgeId ? [e.edgeId] : []));
 
-const { data, err, isLoading } = useListExtensionDetails(chromeExtensionIds);
-const sortedExtensions = computed(() => {
-  if (!data.value?.length) return [];
+const { data, isLoading } = useListExtensionDetails(
+  chromeIds,
+  firefoxSlugs,
+  edgeIds,
+);
 
-  return [...data.value]
-    .filter((item) => item != null)
-    .map((item) => ({
-      ...item,
-      // Sort based on the user count weighted by the rating
-      sortKey: ((item.rating ?? 5) / 5) * item.weeklyActiveUsers,
-    }))
-    .filter((item) => !!item)
-    .sort((l, r) => r.sortKey - l.sortKey);
-});
-
-function getStoreUrl(extension: ChromeExtension) {
-  const url = new URL(extension.storeUrl);
+function addUtmSource(storeUrl: string): string {
+  const url = new URL(storeUrl);
   url.searchParams.set('utm_source', 'wxt.dev');
   return url.href;
 }
+
+const sortedExtensions = computed((): ListedExtension[] => {
+  if (!data.value) return [];
+
+  const chromeById = new Map(
+    (data.value.chrome ?? []).filter(Boolean).map((e) => [e.id, e]),
+  );
+  const firefoxBySlug = new Map(
+    (data.value.firefox ?? []).filter(Boolean).map((e) => [e.id, e]),
+  );
+  const edgeById = new Map(
+    (data.value.edge ?? []).filter(Boolean).map((e) => [e.id, e]),
+  );
+
+  const results: ListedExtension[] = [];
+
+  for (const entry of extensionEntries) {
+    const chrome = entry.chromeId ? chromeById.get(entry.chromeId) : undefined;
+    const firefox = entry.firefoxSlug
+      ? firefoxBySlug.get(entry.firefoxSlug)
+      : undefined;
+    const edge = entry.edgeId ? edgeById.get(entry.edgeId) : undefined;
+
+    if (!chrome && !firefox && !edge) continue;
+
+    const primary = chrome ?? firefox ?? edge!;
+    const users =
+      (chrome?.users ?? 0) + (firefox?.users ?? 0) + (edge?.users ?? 0);
+    const rating = chrome?.rating ?? firefox?.rating ?? edge?.rating;
+
+    const stores: StoreLink[] = [];
+    if (chrome) {
+      stores.push({ label: 'Chrome', url: addUtmSource(chrome.storeUrl) });
+    }
+    if (firefox) {
+      stores.push({ label: 'Firefox', url: addUtmSource(firefox.storeUrl) });
+    }
+    if (edge) {
+      stores.push({ label: 'Edge', url: addUtmSource(edge.storeUrl) });
+    }
+
+    results.push({
+      id:
+        entry.chromeId ??
+        (entry.firefoxSlug
+          ? `firefox:${entry.firefoxSlug}`
+          : `edge:${entry.edgeId}`),
+      name: primary.name,
+      iconUrl: primary.iconUrl,
+      shortDescription: primary.shortDescription,
+      users,
+      rating,
+      stores,
+    });
+  }
+
+  const score = (e: ListedExtension) => ((e.rating ?? 5) / 5) * e.users;
+  return results.sort((a, b) => score(b) - score(a));
+});
+
+function formatUsers(n: number): string {
+  return `${n.toLocaleString()} users`;
+}
+
+function formatStars(r: number): string {
+  const rounded = Math.round(r * 10) / 10;
+  return `${rounded % 1 === 0 ? rounded.toFixed(0) : rounded.toFixed(1)} stars`;
+}
 </script>
 
 <template>
-  <section class="vp-doc">
-    <div class="container">
-      <h2 id="whos-using-wxt">Who's Using WXT?</h2>
-      <p>
-        Battle tested and ready for production. Explore chrome extensions made
-        with WXT.
-      </p>
-      <p v-if="isLoading" style="text-align: center; opacity: 50%">
-        Loading...
-      </p>
-      <p
-        v-else-if="err || sortedExtensions.length === 0"
-        style="text-align: center; opacity: 50%"
-      >
-        Failed to load extension details.
-      </p>
-      <ul v-else>
-        <li
-          v-for="extension of sortedExtensions"
-          :key="extension.id"
-          class="relative"
+  <p v-if="isLoading" style="text-align: center; opacity: 50%">Loading...</p>
+  <p
+    v-else-if="sortedExtensions.length === 0"
+    style="text-align: center; opacity: 50%"
+  >
+    Failed to load extension details.
+  </p>
+  <ul v-else class="extension-grid">
+    <li v-for="extension of sortedExtensions" :key="extension.id">
+      <img
+        :src="extension.iconUrl"
+        :alt="`${extension.name} icon`"
+        referrerpolicy="no-referrer"
+      />
+      <div class="card-content">
+        <a
+          :href="extension.stores[0]?.url ?? '#'"
+          target="_blank"
+          :title="extension.name"
+          class="extension-name"
+          >{{ extension.name }}</a
         >
-          <img
-            :src="extension.iconUrl"
-            :alt="`${extension.name} icon`"
-            referrerpolicy="no-referrer"
-          />
-          <div class="relative">
-            <a
-              :href="getStoreUrl(extension)"
-              target="_blank"
-              :title="extension.name"
-              class="extension-name"
-              >{{ extension.name }}</a
-            >
-            <p class="description" :title="extension.shortDescription">
-              {{ extension.shortDescription }}
-            </p>
-          </div>
-          <p class="user-count">
-            <span>{{ extension.weeklyActiveUsers.toLocaleString() }} users</span
-            ><template v-if="extension.rating != null"
-              >,
-              <span>{{ extension.rating }} stars</span>
+        <p class="description" :title="extension.shortDescription">
+          {{ extension.shortDescription }}
+        </p>
+        <div v-if="extension.stores.length > 0" class="store-stats">
+          <p class="store-stats-info">
+            <span>{{ formatUsers(extension.users) }}</span>
+            <template v-if="extension.rating">
+              <span class="store-stats-sep" aria-hidden="true">,</span>
+              <span>{{ formatStars(extension.rating) }}</span>
             </template>
           </p>
-        </li>
-      </ul>
-      <p class="centered pr">
-        <a
-          href="https://github.com/wxt-dev/wxt/edit/main/docs/.vitepress/components/UsingWxtSection.vue"
-          target="_blank"
-          >Open a PR</a
-        >
-        to add your extension to the list!
-      </p>
-    </div>
-  </section>
+          <p class="store-stats-sep" aria-hidden="true">&middot;</p>
+          <p class="store-links">
+            <template v-for="(store, i) of extension.stores" :key="store.label">
+              <a
+                :href="store.url"
+                target="_blank"
+                class="store-link"
+                :title="store.label"
+                >{{ store.label }}</a
+              >
+              <span
+                v-if="i < extension.stores.length - 1"
+                class="store-stats-sep"
+                aria-hidden="true"
+                >,&nbsp;</span
+              >
+            </template>
+          </p>
+        </div>
+      </div>
+    </li>
+  </ul>
+  <p class="centered pr">
+    <a
+      href="https://github.com/wxt-dev/wxt/edit/main/docs/assets/extension-showcase.yml"
+      target="_blank"
+      >Open a PR</a
+    >
+    to add your extension to the list!
+  </p>
 </template>
 
 <style scoped>
-.vp-doc {
-  padding: 0 24px;
-}
-
-@media (min-width: 640px) {
-  .vp-doc {
-    padding: 0 48px;
-  }
-}
-
-@media (min-width: 960px) {
-  .vp-doc {
-    padding: 0 64px;
-  }
-}
-
-.container {
-  max-width: 1152px;
-  margin: 0 auto;
-  display: flex;
-  flex-direction: column;
-}
-
-li img {
+.extension-grid > li > img {
   width: 116px;
   height: 116px;
   padding: 16px;
@@ -144,7 +190,7 @@ li img {
   background-color: var(--vp-c-default-soft);
 }
 
-ul {
+.extension-grid {
   display: grid;
   grid-template-columns: repeat(1, 1fr);
   align-items: stretch;
@@ -154,12 +200,12 @@ ul {
   padding: 0;
 }
 @media (min-width: 960px) {
-  ul {
+  .extension-grid {
     grid-template-columns: repeat(2, 1fr);
   }
 }
 
-li {
+.extension-grid > li {
   margin: 0 !important;
   padding: 16px;
   display: flex;
@@ -167,28 +213,68 @@ li {
   border-radius: 12px;
   flex: 1;
   gap: 24px;
-  align-items: center;
+  align-items: stretch;
 }
 
 .centered {
   text-align: center;
 }
 
-li a,
-li .user-count,
-li .description {
+.extension-grid > li .description {
   padding: 0;
   margin: 0;
 }
-li .user-count {
-  opacity: 70%;
-  font-size: small;
-  position: absolute;
-  bottom: 12px;
-  right: 16px;
+
+.extension-grid > li .card-content {
+  flex: 1;
+  min-width: 0;
+  display: flex;
+  flex-direction: column;
+  gap: 6px;
+  padding-right: 0;
 }
 
-li a {
+.store-stats {
+  margin-top: auto;
+  padding-top: 6px;
+  display: flex;
+  flex-wrap: wrap;
+  justify-content: flex-end;
+  align-items: baseline;
+  column-gap: 6px;
+  row-gap: 4px;
+  text-align: right;
+  font-size: 12px;
+  line-height: 1.45;
+  opacity: 0.72;
+  color: var(--vp-c-text-2);
+}
+
+.store-stats-info {
+  display: inline;
+}
+
+.store-stats-sep {
+  opacity: 0.45;
+  user-select: none;
+}
+
+.store-links {
+  display: inline;
+}
+
+.store-link {
+  text-decoration: none;
+  color: inherit;
+  cursor: pointer;
+}
+
+.store-link:hover {
+  color: var(--vp-c-text-1);
+  text-decoration: underline;
+}
+
+.extension-grid > li .extension-name {
   display: -webkit-box;
   -webkit-line-clamp: 1;
   -webkit-box-orient: vertical;
@@ -197,33 +283,23 @@ li a {
   padding: 0;
   margin: 0;
   text-decoration: none;
+  font-size: large;
 }
-li a:hover {
+
+.extension-grid > li .extension-name:hover {
   text-decoration: underline;
 }
 
-li div {
-  flex: 1;
-}
-
-li .description {
+.extension-grid > li .description {
   opacity: 90%;
   display: -webkit-box;
   -webkit-line-clamp: 2;
   -webkit-box-orient: vertical;
   overflow: hidden;
-  margin-bottom: 16px;
-}
-
-li .extension-name {
-  font-size: large;
+  margin-bottom: 0 !important;
 }
 
 .pr {
   opacity: 70%;
 }
-
-.relative {
-  position: relative;
-}
 </style>

docs/.vitepress/composables/useBlogDate.ts

@@ -0,0 +1,15 @@
+import { computed, toValue, MaybeRefOrGetter } from 'vue';
+
+const MONTH_FORMATTER = new Intl.DateTimeFormat(
+  globalThis?.navigator?.language,
+  {
+    month: 'long',
+  },
+);
+
+export default function (date: MaybeRefOrGetter<Date | string>) {
+  return computed(() => {
+    const d = new Date(toValue(date));
+    return `${MONTH_FORMATTER.format(d)} ${d.getDate()}, ${d.getFullYear()}`;
+  });
+}

docs/.vitepress/composables/useListExtensionDetails.ts

@@ -1,47 +1,84 @@
 import { ref } from 'vue';
 
-export interface ChromeExtension {
+export interface Extension {
   id: string;
   name: string;
   iconUrl: string;
-  weeklyActiveUsers: number;
   shortDescription: string;
   storeUrl: string;
   rating: number | undefined;
+  users: number;
+}
+
+export interface ExtensionResults {
+  chrome: Extension[];
+  firefox: Extension[];
+  edge: Extension[];
 }
 
 const operationName = 'WxtDocsUsedBy';
-const query = `query ${operationName}($ids:[String!]!) {
-  chromeExtensions(ids: $ids) {
+const query = `query ${operationName}($chromeIds: [String!]!, $firefoxIds: [String!]!, $edgeIds: [String!]!) {
+  chromeExtensions(ids: $chromeIds) {
     id
-    name
-    iconUrl
-    weeklyActiveUsers
-    shortDescription
-    storeUrl
-    rating
+    ...ExtensionData
   }
+  firefoxAddons(ids: $firefoxIds) {
+    id: slug
+    ...ExtensionData
+  }
+  edgeAddons(ids: $edgeIds) {
+    id
+    ...ExtensionData
+  }
+}
+
+fragment ExtensionData on Extension {
+  name
+  iconUrl
+  shortDescription
+  storeUrl
+  rating
+  users
 }`;
 
-export default function (ids: string[]) {
-  const data = ref<ChromeExtension[]>();
+export default function (
+  chromeIds: string[],
+  firefoxSlugs: string[],
+  edgeIds: string[],
+) {
+  const data = ref<ExtensionResults>();
   const err = ref<unknown>();
   const isLoading = ref(true);
 
+  if (
+    chromeIds.length === 0 &&
+    firefoxSlugs.length === 0 &&
+    edgeIds.length === 0
+  ) {
+    data.value = { chrome: [], firefox: [], edge: [] };
+    isLoading.value = false;
+    return { data, err, isLoading };
+  }
+
   fetch('https://queue.wxt.dev/api', {
     method: 'POST',
     body: JSON.stringify({
       operationName,
       query,
-      variables: { ids },
+      variables: { chromeIds, firefoxIds: firefoxSlugs, edgeIds },
     }),
+    headers: {
+      'Content-Type': 'application/json',
+    },
   })
     .then(async (res) => {
       isLoading.value = false;
-      const {
-        data: { chromeExtensions },
-      } = await res.json();
-      data.value = chromeExtensions;
+      const { data: responseData } = await res.json();
+      data.value = {
+        chrome: responseData.chromeExtensions ?? [],
+        firefox: responseData.firefoxAddons ?? [],
+        edge: responseData.edgeAddons ?? [],
+      };
       err.value = undefined;
     })
     .catch((error) => {
@@ -51,9 +88,5 @@ export default function (ids: string[]) {
       err.value = error;
     });
 
-  return {
-    data,
-    err,
-    isLoading,
-  };
+  return { data, err, isLoading };
 }

docs/.vitepress/config.ts

@@ -1,155 +1,281 @@
+import { Feed } from 'feed';
+// @ts-expect-error; It isn't TypeScript lib
+import footnote from 'markdown-it-footnote';
+import fs, { readFile } from 'node:fs/promises';
+import { join } from 'node:path';
 import { DefaultTheme, defineConfig } from 'vitepress';
-import { generateCliDocs } from './plugins/generate-cli-docs';
-import typedocSidebar from '../api/typedoc-sidebar.json';
+import addKnowledge from 'vitepress-knowledge';
+import {
+  groupIconMdPlugin,
+  groupIconVitePlugin,
+  localIconLoader,
+} from 'vitepress-plugin-group-icons';
+import llmstxt from 'vitepress-plugin-llms';
+import { version as analyticsVersion } from '../../packages/analytics/package.json';
+import { version as autoIconsVersion } from '../../packages/auto-icons/package.json';
+import { version as i18nVersion } from '../../packages/i18n/package.json';
+import { version as runnerVersion } from '../../packages/runner/package.json';
+import { version as storageVersion } from '../../packages/storage/package.json';
+import { version as unocssVersion } from '../../packages/unocss/package.json';
+import { version as wxtVersion } from '../../packages/wxt/package.json';
+import { version as isBackgroundVersion } from '../../packages/is-background/package.json';
+import typedocSidebar from '../api/reference/typedoc-sidebar.json';
+import { meta, script } from './utils/head';
+import {
+  menuGroup,
+  menuItem,
+  menuRoot,
+  navItem,
+  prepareTypedocSidebar,
+} from './utils/menus';
 
-const filteredTypedocSidebar = typedocSidebar.filter(
-  (item) => item.text !== 'API',
-);
-// Typedoc's markdown theme adds collapse: true to all our items, event ones without any children,
-// so they need to be removed.
-function removeCollapsedWithNoItems(items: DefaultTheme.SidebarItem[]) {
-  for (const item of items) {
-    if (item.items) removeCollapsedWithNoItems(item.items);
-    else delete item.collapsed;
-  }
-}
-removeCollapsedWithNoItems(filteredTypedocSidebar);
+const origin = 'https://wxt.dev';
 
 const title = 'Next-gen Web Extension Framework';
 const titleSuffix = ' – WXT';
-
 const description =
-  "WXT provides the best developer experience, making it quick, easy, and fun to develop chrome extensions for all browsers. With built-in utilities for building, zipping, and publishing your extension, it's easy to get started.";
+  "WXT provides the best developer experience, making it quick, easy, and fun to develop web extensions. With built-in utilities for building, zipping, and publishing your extension, it's easy to get started.";
 const ogTitle = `${title}${titleSuffix}`;
-const ogUrl = 'https://wxt.dev';
-const ogImage = 'https://wxt.dev/social-preview.png';
+const ogUrl = origin;
+const ogImage = `${origin}/social-preview.png`;
+
+const otherPackages = {
+  analytics: analyticsVersion,
+  'auto-icons': autoIconsVersion,
+  i18n: i18nVersion,
+  storage: storageVersion,
+  unocss: unocssVersion,
+  runner: runnerVersion,
+  'is-background': isBackgroundVersion,
+};
+
+const knowledge = addKnowledge<DefaultTheme.Config>({
+  serverUrl: 'https://knowledge.wxt.dev',
+  paths: {
+    '/': 'docs',
+    '/api/': 'api-reference',
+    '/blog/': 'blog',
+  },
+  layoutSelectors: {
+    blog: '.container-content',
+  },
+  pageSelectors: {
+    'examples.md': '#VPContent > .VPPage',
+    'blog.md': '#VPContent > .VPPage',
+  },
+});
 
 // https://vitepress.dev/reference/site-config
 export default defineConfig({
+  extends: knowledge,
+
   titleTemplate: `:title${titleSuffix}`,
   title: 'WXT',
   description,
   vite: {
     clearScreen: false,
-    plugins: [generateCliDocs()],
+    //TODO: REMOVE THIS @TS-EXPECT-ERROR AFTER BUMP VITEPRESS TO V2.0
+    plugins: [
+      // @ts-expect-error: Vite version mismatch between this project and the plugin
+      llmstxt(),
+      // @ts-expect-error: Vite version mismatch between this project and the plugin
+      groupIconVitePlugin({
+        customIcon: {
+          'wxt.config.ts': localIconLoader(
+            import.meta.url,
+            '../public/logo.svg',
+          ),
+        },
+      }),
+      {
+        name: 'yaml-loader',
+        load: {
+          handler: async (id) => {
+            if (id.endsWith('.yml') || id.endsWith('.yaml')) {
+              const obj = Bun.YAML.parse(await readFile(id, 'utf8'));
+              return `export default ${JSON.stringify(obj)}`;
+            }
+          },
+        },
+      },
+    ],
   },
   lastUpdated: true,
   sitemap: {
-    hostname: 'https://wxt.dev',
+    hostname: origin,
+  },
+
+  async buildEnd(site) {
+    // @ts-expect-error: knowledge.buildEnd is not typed, but it exists.
+    await knowledge.buildEnd(site);
+
+    // Only construct the RSS document for production builds
+    const { default: blogDataLoader } = await import('./loaders/blog.data');
+    const posts = await blogDataLoader.load();
+    const feed = new Feed({
+      copyright: 'MIT',
+      id: 'wxt',
+      title: 'WXT Blog',
+      link: `${origin}/blog`,
+    });
+    posts.forEach((post) => {
+      feed.addItem({
+        date: post.frontmatter.date,
+        link: new URL(post.url, origin).href,
+        title: post.frontmatter.title,
+        description: post.frontmatter.description,
+      });
+    });
+    // console.log('rss.xml:');
+    // console.log(feed.rss2());
+    await fs.writeFile(join(site.outDir, 'rss.xml'), feed.rss2());
   },
 
   head: [
-    ['meta', { property: 'og:type', content: 'website' }],
-    ['meta', { property: 'og:title', content: ogTitle }],
-    ['meta', { property: 'og:image', content: ogImage }],
-    ['meta', { property: 'og:url', content: ogUrl }],
-    ['meta', { property: 'og:description', content: description }],
-    ['meta', { name: 'twitter:card', content: 'summary_large_image' }],
-    [
-      'script',
-      {
-        async: '',
-        'data-website-id': 'c1840c18-a12c-4a45-a848-55ae85ef7915',
-        src: 'https://umami.aklinker1.io/script.js',
-      },
-    ],
+    meta('og:type', 'website'),
+    meta('og:title', ogTitle),
+    meta('og:image', ogImage),
+    meta('og:url', ogUrl),
+    meta('og:description', description),
+    meta('twitter:card', 'summary_large_image', { useName: true }),
+    script('https://umami.aklinker1.io/script.js', {
+      'data-website-id': 'c1840c18-a12c-4a45-a848-55ae85ef7915',
+      async: '',
+    }),
   ],
 
+  markdown: {
+    config: (md) => {
+      md.use(footnote);
+      md.use(groupIconMdPlugin);
+    },
+    languageAlias: {
+      mjs: 'js',
+    },
+  },
+
   themeConfig: {
     // https://vitepress.dev/reference/default-theme-config
     logo: {
       src: '/logo.svg',
       alt: 'WXT logo',
     },
+
+    footer: {
+      message: [
+        '<span class="netlify-badge"><a class="light-netlify" href="https://www.netlify.com"><img src="/netlify-badge-light.svg" alt="Deploys by Netlify" /></a><a class="dark-netlify" href="https://www.netlify.com"><img src="/netlify-badge-dark.svg" alt="Deploys by Netlify" /></a></span>',
+        'Released under the <a href="https://github.com/wxt-dev/wxt/blob/main/LICENSE">MIT License</a>.',
+      ].join('<br/>'),
+      copyright:
+        'Copyright © 2023-present <a href="https://github.com/aklinker1">Aaron Klinker</a>',
+    },
+
     editLink: {
       pattern: 'https://github.com/wxt-dev/wxt/edit/main/docs/:path',
     },
+
     search: {
       provider: 'local',
     },
 
-    nav: [
-      { text: 'Guide', link: '/guide/installation.md' },
-      { text: 'Entrypoints', link: '/entrypoints/background.md' },
-      { text: 'Examples', link: '/examples.md' },
-      { text: 'API', link: '/api/cli.md' },
-    ],
-
-    sidebar: {
-      '/guide/': [
-        {
-          text: 'Guide',
-          items: [
-            { text: 'Introduction', link: '/guide/introduction.md' },
-            { text: 'Installation', link: '/guide/installation.md' },
-            { text: 'Configuration', link: '/guide/configuration.md' },
-            { text: 'Entrypoints', link: '/guide/entrypoints.md' },
-            { text: 'Manifest.json', link: '/guide/manifest.md' },
-            { text: 'Extension APIs', link: '/guide/extension-apis.md' },
-            { text: 'Storage', link: '/guide/storage.md' },
-            { text: 'Assets', link: '/guide/assets.md' },
-            { text: 'Content Script UI', link: '/guide/content-script-ui.md' },
-            { text: 'Multiple Browsers', link: '/guide/multiple-browsers.md' },
-            { text: 'ES Modules', link: '/guide/esm.md' },
-            { text: 'Auto-imports', link: '/guide/auto-imports.md' },
-            { text: 'Vite', link: '/guide/vite.md' },
-            { text: 'Remote Code', link: '/guide/remote-code.md' },
-            { text: 'Publishing', link: '/guide/publishing.md' },
-            { text: 'Handling Updates', link: '/guide/handling-updates.md' },
-            { text: 'Development', link: '/guide/development.md' },
-            { text: 'Testing', link: '/guide/testing.md' },
-          ],
-        },
-        {
-          text: 'Other',
-          items: [
-            { text: 'Migrate to WXT', link: '/guide/migrate-to-wxt.md' },
-            { text: 'Compare', link: '/guide/compare.md' },
-          ],
-        },
-      ],
-      '/entrypoints/': [
-        {
-          text: 'Entrypoints',
-          items: [
-            { text: 'Background', link: '/entrypoints/background.md' },
-            { text: 'Bookmarks', link: '/entrypoints/bookmarks.md' },
-            {
-              text: 'Content Scripts',
-              link: '/entrypoints/content-scripts.md',
-            },
-            { text: 'CSS', link: '/entrypoints/css.md' },
-            { text: 'Devtools', link: '/entrypoints/devtools.md' },
-            { text: 'History', link: '/entrypoints/history.md' },
-            { text: 'Newtab', link: '/entrypoints/newtab.md' },
-            { text: 'Options', link: '/entrypoints/options.md' },
-            { text: 'Popup', link: '/entrypoints/popup.md' },
-            { text: 'Sandbox', link: '/entrypoints/sandbox.md' },
-            { text: 'Side Panel', link: '/entrypoints/sidepanel.md' },
-            { text: 'Unlisted Pages', link: '/entrypoints/unlisted-pages.md' },
-            {
-              text: 'Unlisted Scripts',
-              link: '/entrypoints/unlisted-scripts.md',
-            },
-          ].sort((l, r) => l.text.localeCompare(r.text)),
-        },
-      ],
-      '/api/': [
-        {
-          items: [
-            { text: 'CLI', link: '/api/cli.md' },
-            {
-              text: 'Modules',
-              items: filteredTypedocSidebar,
-            },
-          ],
-        },
-      ],
-    },
-
     socialLinks: [
       { icon: 'discord', link: 'https://discord.gg/ZFsZqGery9' },
       { icon: 'github', link: 'https://github.com/wxt-dev/wxt' },
     ],
+
+    nav: [
+      navItem('Guide', '/guide/installation'),
+      navItem('Examples', '/examples'),
+      navItem('API', '/api/reference/wxt'),
+      navItem('Blog', '/blog'),
+      navItem(`v${wxtVersion}`, [
+        navItem('wxt', [
+          navItem(`v${wxtVersion}`, '/'),
+          navItem(
+            `Changelog`,
+            'https://github.com/wxt-dev/wxt/blob/main/packages/wxt/CHANGELOG.md',
+          ),
+        ]),
+        navItem(
+          'Other Packages',
+          Object.entries(otherPackages).map(([name, version]) =>
+            navItem(`@wxt-dev/${name} — ${version}`, `/${name}`),
+          ),
+        ),
+      ]),
+    ],
+
+    sidebar: {
+      '/guide/': menuRoot([
+        menuGroup('Get Started', '/guide/', [
+          menuItem('Introduction', 'introduction.md'),
+          menuItem('Installation', 'installation.md'),
+        ]),
+        menuGroup('Essentials', '/guide/essentials/', [
+          menuItem('Project Structure', 'project-structure.md'),
+          menuItem('Entrypoints', 'entrypoints.md'),
+          menuGroup(
+            'Configuration',
+            '/guide/essentials/config/',
+            [
+              menuItem('Manifest', 'manifest.md'),
+              menuItem('Browser Startup', 'browser-startup.md'),
+              menuItem('Auto-imports', 'auto-imports.md'),
+              menuItem('Environment Variables', 'environment-variables.md'),
+              menuItem('Runtime Config', 'runtime.md'),
+              menuItem('Vite', 'vite.md'),
+              menuItem('Build Mode', 'build-mode.md'),
+              menuItem('TypeScript', 'typescript.md'),
+              menuItem('Hooks', 'hooks.md'),
+              menuItem('Entrypoint Loaders', 'entrypoint-loaders.md'),
+            ],
+            true,
+          ),
+          menuItem('Extension APIs', 'extension-apis.md'),
+          menuItem('Assets', 'assets.md'),
+          menuItem('Target Different Browsers', 'target-different-browsers.md'),
+          menuItem('Content Scripts', 'content-scripts.md'),
+          menuItem('Storage', 'storage.md'),
+          menuItem('Messaging', 'messaging.md'),
+          menuItem('I18n', 'i18n.md'),
+          menuItem('Favicons', 'favicons.md'),
+          menuItem('Scripting', 'scripting.md'),
+          menuItem('WXT Modules', 'wxt-modules.md'),
+          menuItem('Frontend Frameworks', 'frontend-frameworks.md'),
+          menuItem('ES Modules', 'es-modules.md'),
+          menuItem('Remote Code', 'remote-code.md'),
+          menuItem('Unit Testing', 'unit-testing.md'),
+          menuItem('E2E Testing', 'e2e-testing.md'),
+          menuItem('Publishing', 'publishing.md'),
+          menuItem('Testing Updates', 'testing-updates.md'),
+        ]),
+        menuGroup('Resources', '/guide/resources/', [
+          menuItem('Compare', 'compare.md'),
+          menuItem('FAQ', 'faq.md'),
+          menuItem('Community', 'community.md'),
+          menuItem('Upgrading WXT', 'upgrading.md'),
+          menuItem('Migrate to WXT', 'migrate.md'),
+          menuItem('How WXT Works', 'how-wxt-works.md'),
+        ]),
+      ]),
+      '/api/': menuRoot([
+        menuGroup(
+          'CLI Reference',
+          '/api/cli/',
+          [
+            menuItem('wxt', 'wxt.md'),
+            menuItem('wxt build', 'wxt-build.md'),
+            menuItem('wxt zip', 'wxt-zip.md'),
+            menuItem('wxt prepare', 'wxt-prepare.md'),
+            menuItem('wxt clean', 'wxt-clean.md'),
+            menuItem('wxt init', 'wxt-init.md'),
+            menuItem('wxt submit', 'wxt-submit.md'),
+            menuItem('wxt submit init', 'wxt-submit-init.md'),
+          ],
+          true,
+        ),
+        menuGroup('API Reference', prepareTypedocSidebar(typedocSidebar), true),
+      ]),
+    },
   },
 });

docs/.vitepress/loaders/blog.data.ts

@@ -0,0 +1,9 @@
+import { type ContentData, createContentLoader } from 'vitepress';
+import { PostFrontmatter } from '../utils/types';
+
+declare const data: Array<ContentData & { frontmatter: PostFrontmatter }>;
+export { data };
+
+export default createContentLoader<
+  Array<ContentData & { frontmatter: PostFrontmatter }>
+>('blog/*.md');

docs/.vitepress/loaders/cli.data.ts

@@ -0,0 +1,58 @@
+import consola from 'consola';
+import spawn from 'nano-spawn';
+import { resolve } from 'node:path';
+import { version } from '../../../packages/wxt/package.json';
+
+const cliDir = resolve('packages/wxt/src/cli/commands');
+const cliDirGlob = resolve(cliDir, '**');
+
+export default {
+  watch: [cliDirGlob],
+  async load() {
+    consola.info(`Generating CLI docs`);
+
+    const [wxt, build, zip, prepare, clean, init, submit, submitInit] =
+      await Promise.all([
+        getWxtHelp(''),
+        getWxtHelp('build'),
+        getWxtHelp('zip'),
+        getWxtHelp('prepare'),
+        getWxtHelp('clean'),
+        getWxtHelp('init'),
+        getPublishExtensionHelp(''),
+        getPublishExtensionHelp('init'),
+      ]);
+
+    consola.success(`Generated CLI docs`);
+    return {
+      wxt,
+      build,
+      zip,
+      prepare,
+      clean,
+      init,
+      submit,
+      submitInit,
+    };
+  },
+};
+
+async function getHelp(command: string): Promise<string> {
+  const args = command.split(' ');
+  const result = await spawn(args[0], [...args.slice(1), '--help'], {
+    cwd: 'packages/wxt',
+  });
+  return result.stdout;
+}
+
+async function getWxtHelp(command: string): Promise<string> {
+  const res = await getHelp(`bun run --silent wxt ${command}`.trim());
+  return res.replaceAll('{{version}}', version);
+}
+
+async function getPublishExtensionHelp(command: string): Promise<string> {
+  const res = await getHelp(
+    `bun run --silent publish-extension ${command}`.trim(),
+  );
+  return res.replace(/\$ publish-extension/g, '$ wxt submit');
+}

docs/.vitepress/plugins/cli.tpl.md

@@ -1,5 +0,0 @@
-# CLI Reference
-
-> Reference generated from `wxt <command> --help`
-
-{{ DOCS }}

docs/.vitepress/plugins/generate-cli-docs.ts

@@ -1,118 +0,0 @@
-import { relative, resolve } from 'node:path';
-import { readFileSync, writeFileSync } from 'node:fs';
-import { format } from 'prettier';
-import consola from 'consola';
-import { execaCommand } from 'execa';
-
-let hasGenerated = false;
-
-const cliDir = resolve('packages/wxt/src/cli/commands');
-const cliDirGlob = resolve(cliDir, '**');
-const cliTemplatePath = resolve('docs/.vitepress/plugins/cli.tpl.md');
-const cliPath = resolve('docs/api/cli.md');
-
-const PREFACE = `<!--
-DO NOT EDIT
-Generated by \`wxt/docs/.vitepress/plugins/generate-config-docs.ts\`
-To make changes to the config reference, update the JSDoc in \`src/core/types/external.ts\`.
--->`;
-
-export function generateCliDocs() {
-  writeFileSync(cliPath, '');
-
-  const generateDocs = async () => {
-    consola.info(`Generating ${relative(process.cwd(), cliPath)}`);
-    try {
-      const res = await execaCommand('pnpm -s wxt --help', {
-        cwd: 'packages/wxt',
-      });
-      const dev = splitInfo(res.stdout);
-      const lines: Array<string | string[]> = [
-        `## \`wxt\``,
-        '```sh',
-        dev.rest,
-        '```',
-      ];
-
-      const commands = await Promise.allSettled(
-        extractCommands(dev.info).map(async (command) => {
-          const res = await execaCommand(`pnpm -s wxt ${command} --help`, {
-            cwd: 'packages/wxt',
-          });
-          const { rest: docs } = splitInfo(res.stdout);
-          return [`## \`wxt ${command}\``, '```sh', docs, '```'];
-        }),
-      );
-      lines.push(
-        ...commands
-          .filter((res) => res.status === 'fulfilled')
-          .map(
-            (res) => (res as unknown as PromiseFulfilledResult<string>).value,
-          ),
-      );
-
-      const text = await format(
-        PREFACE +
-          '\n\n' +
-          readFileSync(cliTemplatePath, 'utf-8').replace(
-            '{{ DOCS }}',
-            lines.flat().join('\n'),
-          ),
-        { parser: 'markdown' },
-      );
-
-      writeFileSync(cliPath, text);
-      consola.success(`Generated ${relative(process.cwd(), cliPath)}`);
-    } catch (err) {
-      consola.fail(`Failed to generate ${relative(process.cwd(), cliPath)}`);
-      consola.error(err.message);
-    }
-  };
-
-  return {
-    name: 'docs:generate-cli-docs',
-    async config() {
-      if (!hasGenerated) {
-        hasGenerated = true;
-        await generateDocs();
-      }
-    },
-    configureServer(server: any) {
-      server.watcher.add(cliDirGlob);
-    },
-    async handleHotUpdate(ctx: { file: string }) {
-      if (ctx.file === cliTemplatePath || ctx.file.includes(cliDir)) {
-        await generateDocs();
-      }
-    },
-  };
-}
-
-function splitInfo(text: string): { info: string; rest: string } {
-  const infoStart = text.indexOf('For more info,');
-  const infoEnd = text.indexOf('\n\nOptions:');
-
-  if (infoStart === -1 || infoEnd === -1) {
-    return { info: '', rest: text };
-  }
-
-  const info = text.substring(infoStart, infoEnd).trim();
-  const rest = text.replace(info, '').trim().replace('\n\n\n\n', '\n\n');
-
-  return { info, rest };
-}
-
-function extractCommands(info: string): string[] {
-  const commands: string[] = [];
-
-  // Split the info by line and iterate through each line
-  info.split('\n').forEach((line) => {
-    // Use regex to capture the command after "$ wxt " and before "--help"
-    const match = line.match(/\$ wxt (\w+) --help/);
-    if (match && match[1]) {
-      commands.push(match[1]);
-    }
-  });
-
-  return commands;
-}

docs/.vitepress/theme/custom.css

@@ -1,77 +1,87 @@
+/* https://github.com/vuejs/vitepress/blob/main/src/client/theme-default/styles/vars.css */
 /* Colors */
 :root {
-  --wxt-c-green: #53bc4a;
-  --wxt-c-green-1: #67d45e;
-  --wxt-c-green-2: #4fa048;
-  --wxt-c-green-3: #447e3f;
-}
+  --wxt-c-green-1: #0b8a00;
+  --wxt-c-green-2: #096600;
+  --wxt-c-green-3: #096600;
+  --wxt-c-green-soft: rgba(11, 138, 0, 0.14);
 
-/* https://github.com/vuejs/vitepress/blob/main/src/client/theme-default/styles/vars.css */
-
-:root {
-  --vp-c-brand: var(--wxt-c-green);
   --vp-c-brand-1: var(--wxt-c-green-1);
   --vp-c-brand-2: var(--wxt-c-green-2);
   --vp-c-brand-3: var(--wxt-c-green-3);
-
-  --vp-button-brand-bg: var(--wxt-c-green);
-  --vp-button-brand-hover-bg: var(--wxt-c-green-2);
-  --vp-button-brand-active-bg: var(--wxt-c-green-3);
-
-  --vp-code-link-color: var(--wxt-c-green);
-
-  /* --vp-c-text-1: var(--wxt-c-green-1); */
-
-  --vp-button-brand-text: var(--vp-c-black);
-  --vp-button-brand-hover-text: var(--vp-c-black);
-  --vp-button-brand-active-text: var(--vp-c-black);
-
-  --vp-custom-block-tip-border: var(--wxt-c-green);
-  --vp-custom-block-tip-text: var(--wxt-c-green);
-
-  /* --vp-code-block-bg: #222422;
-  --vp-code-copy-code-bg: #313431;
-  --vp-code-copy-code-hover-bg: #3c403c; */
-
-  --vp-custom-block-tip-bg: var(--vp-code-block-bg);
-  --vp-custom-block-info-bg: var(--vp-code-block-bg);
-
-  --vp-code-color: #476582;
-}
-
-.vp-doc a {
-  color: var(--wxt-c-green);
+  --vp-c-brand-soft: var(--wxt-c-green-soft);
 }
 
 .dark {
-  --vp-c-bg: #131413;
-
-  --vp-c-bg-soft: #1a1b1a;
-  --vp-c-bg-soft-up: #1f201f;
-  --vp-c-bg-soft-down: #262926;
-  --vp-c-bg-soft-mute: #242424;
-
-  --vp-c-bg-alt: #171817;
-
-  --vp-c-default: #313136;
-  --vp-c-default-1: #3a3a3c;
-  --vp-c-default-2: #505053;
-  --vp-c-default-3: #2c2c30;
-  --vp-c-default-soft: #252529;
-
-  --vp-code-block-bg: #191a19;
-  --vp-code-copy-code-bg: #212321;
-  --vp-code-copy-code-hover-bg: #292d29;
-
-  --vp-custom-block-info-bg: #191a19;
-
-  --vp-code-color: #c9def1;
+  --wxt-c-green-1: #67d45e;
+  --wxt-c-green-2: #329929;
+  --wxt-c-green-3: #21651b;
+  --wxt-c-green-soft: rgba(103, 212, 94, 0.14);
 }
 
-.vp-doc .no-vertical-dividers th,
-.vp-doc .no-vertical-dividers td {
-  border: none;
+* {
+  margin: 0;
+  padding: 0;
+  box-sizing: border-box;
 }
-.vp-doc .no-vertical-dividers tr {
-  border: 1px solid var(--vp-c-divider);
+
+/* Customize Individual Components */
+.vp-doc .no-vertical-dividers {
+  th,
+  td {
+    border: none;
+  }
+
+  tr {
+    border: 1px solid var(--vp-c-divider);
+  }
+}
+
+body {
+  overflow-y: scroll;
+}
+
+.light-netlify {
+  display: inline-flex;
+}
+
+.dark .light-netlify {
+  display: none;
+}
+
+.dark-netlify {
+  display: none;
+}
+
+.dark .dark-netlify {
+  display: inline-flex;
+}
+
+/* Add Aaron's favorite pic from Artemis II to the hero section because it's cool. */
+.dark .VPHome::before {
+  content: '';
+  position: absolute;
+  background-image: url('../../assets/art002e009298.jpg');
+  opacity: 50%;
+  width: 100%;
+  height: 110vh;
+  background-size: cover;
+  background-position: 90%;
+}
+
+.dark .VPHome::after {
+  content: '';
+  position: absolute;
+  width: 100%;
+  height: 10vh;
+  top: 100vh;
+  background: linear-gradient(to bottom, transparent, var(--vp-c-bg));
+}
+
+.item {
+  z-index: 1;
+}
+
+.VPSidebar .curtain {
+  z-index: 2;
 }

docs/.vitepress/theme/index.ts

@@ -2,15 +2,23 @@ import DefaultTheme from 'vitepress/theme';
 import Icon from '../components/Icon.vue';
 import EntrypointPatterns from '../components/EntrypointPatterns.vue';
 import UsingWxtSection from '../components/UsingWxtSection.vue';
-import ExampleList from '../components/ExampleList.vue';
+import ExampleSearch from '../components/ExampleSearch.vue';
+import BlogLayout from '../components/BlogLayout.vue';
 import './custom.css';
+import 'virtual:group-icons.css';
+import type { EnhanceAppContext } from 'vitepress/client';
+import { setupCodeGroupSync } from '../utils/code-groups-sync';
 
 export default {
   extends: DefaultTheme,
-  enhanceApp(ctx) {
-    ctx.app.component('Icon', Icon);
-    ctx.app.component('EntrypointPatterns', EntrypointPatterns);
-    ctx.app.component('UsingWxtSection', UsingWxtSection);
-    ctx.app.component('ExampleList', ExampleList);
+  enhanceApp(ctx: EnhanceAppContext) {
+    ctx.app
+      .component('Icon', Icon)
+      .component('EntrypointPatterns', EntrypointPatterns)
+      .component('UsingWxtSection', UsingWxtSection)
+      .component('ExampleSearch', ExampleSearch)
+      .component('blog', BlogLayout);
+
+    setupCodeGroupSync();
   },
 };

docs/.vitepress/utils/code-groups-sync.ts

@@ -0,0 +1,73 @@
+const CODE_GROUP_SELECTORS = {
+  root: '.vp-code-group',
+  input: '.vp-code-group .tabs input',
+  label: '.tabs label',
+} as const;
+
+function getTabTitle(label: HTMLLabelElement) {
+  return label.dataset.title?.trim() || label.textContent?.trim();
+}
+
+function getCodeGroupTitle(input: HTMLInputElement) {
+  const label = input.parentElement?.querySelector<HTMLLabelElement>(
+    `label[for="${input.id}"]`,
+  );
+
+  return label ? getTabTitle(label) : undefined;
+}
+
+function findCodeGroupTabIndex(group: HTMLElement, title: string) {
+  return Array.from(
+    group.querySelectorAll<HTMLLabelElement>(CODE_GROUP_SELECTORS.label),
+  ).findIndex((label) => getTabTitle(label) === title);
+}
+
+function syncCodeGroupSelection(group: HTMLElement, title: string) {
+  const targetIndex = findCodeGroupTabIndex(group, title);
+
+  if (targetIndex < 0) return;
+
+  const blocks = group.querySelector('.blocks');
+  const targetBlock = blocks?.children[targetIndex];
+  if (!blocks || !targetBlock || targetBlock.classList.contains('active'))
+    return;
+
+  blocks.querySelector('.active')?.classList.remove('active');
+  targetBlock.classList.add('active');
+
+  const input = group.querySelectorAll<HTMLInputElement>(
+    CODE_GROUP_SELECTORS.input,
+  )[targetIndex];
+  if (input) input.checked = true;
+}
+
+function syncCodeGroupTabs(event: Event) {
+  const target = event.target;
+  if (
+    !(target instanceof HTMLInputElement) ||
+    !target.matches(CODE_GROUP_SELECTORS.input)
+  )
+    return;
+
+  const activeGroup = target.closest(CODE_GROUP_SELECTORS.root);
+  const activeTitle = getCodeGroupTitle(target);
+  if (!activeTitle) return;
+
+  document
+    .querySelectorAll<HTMLElement>(CODE_GROUP_SELECTORS.root)
+    .forEach((group) => {
+      if (group === activeGroup) return;
+
+      syncCodeGroupSelection(group, activeTitle);
+    });
+}
+
+/**
+ * Keeps every code group on the page in sync: selecting a package manager (or
+ * any tab) in one group switches the matching tab in all the other groups.
+ */
+export function setupCodeGroupSync() {
+  if (typeof window === 'undefined') return;
+
+  window.addEventListener('change', syncCodeGroupTabs, true);
+}

docs/.vitepress/utils/head.ts

@@ -0,0 +1,28 @@
+import type { HeadConfig } from 'vitepress';
+
+export function meta(
+  property: string,
+  content: string,
+  options?: { useName: boolean },
+): HeadConfig {
+  return [
+    'meta',
+    {
+      [options?.useName ? 'name' : 'property']: property,
+      content,
+    },
+  ];
+}
+
+export function script(
+  src: string,
+  props: Record<string, string> = {},
+): HeadConfig {
+  return [
+    'script',
+    {
+      ...props,
+      src,
+    },
+  ];
+}

docs/.vitepress/utils/menus.ts

@@ -0,0 +1,95 @@
+import { DefaultTheme } from 'vitepress';
+
+type SidebarItem = DefaultTheme.SidebarItem;
+type NavItemWithChildren = DefaultTheme.NavItemWithChildren;
+type NavItemChildren = DefaultTheme.NavItemChildren;
+
+export function navItem(text: string): NavItemChildren;
+export function navItem(text: string, link: string): NavItemChildren;
+export function navItem(text: string, items: any[]): NavItemWithChildren;
+export function navItem(text: string, arg2?: unknown): any {
+  if (typeof arg2 === 'string') {
+    return { text, link: arg2 };
+  } else if (Array.isArray(arg2)) {
+    return { text, items: arg2 };
+  }
+  return { text };
+}
+
+export function menuRoot(items: SidebarItem[]) {
+  return items.map((item) => {
+    // item.collapsed = false; // uncomment to expand all level-0 items
+    return item;
+  });
+}
+
+export function menuGroup(
+  text: string,
+  items: SidebarItem[],
+  collapsible?: boolean,
+): SidebarItem;
+export function menuGroup(
+  text: string,
+  base: string,
+  items: SidebarItem[],
+  collapsible?: boolean,
+): SidebarItem;
+export function menuGroup(
+  text: string,
+  a: string | SidebarItem[],
+  b?: SidebarItem[] | boolean,
+  c?: boolean,
+): SidebarItem {
+  if (typeof a === 'string' && Array.isArray(b)) {
+    return {
+      text,
+      base: a,
+      items: b,
+      collapsed: c,
+    };
+  }
+  if (typeof a !== 'string' && !Array.isArray(b))
+    return {
+      text,
+      items: a,
+      collapsed: b,
+    };
+
+  throw Error('Unknown overload');
+}
+
+export function menuItem(
+  text: string,
+  link: string,
+  items?: SidebarItem[],
+): SidebarItem {
+  if (items) {
+    return { text, link, items };
+  }
+  return { text, link };
+}
+
+/** Clean up and add badges to typedoc leaf sections */
+export function prepareTypedocSidebar(items: SidebarItem[]) {
+  // skip contents file
+  const filtered = items.slice(1);
+
+  // remove Typedoc's collapse: true from text nodes
+  const prepareItems = (items: DefaultTheme.SidebarItem[], depth = 0) => {
+    for (const item of items) {
+      if (item.items) {
+        prepareItems(item.items, depth + 1);
+        const hasLeaves = item.items.some((item) => !item.items);
+        if (hasLeaves) {
+          item.text += ` <span class="badge">${item.items.length}</span>`;
+        }
+      } else {
+        delete item.collapsed;
+      }
+    }
+  };
+
+  prepareItems(filtered);
+
+  return filtered;
+}

docs/.vitepress/utils/types.ts

@@ -0,0 +1,32 @@
+import { ContentData } from 'vitepress';
+
+export interface Example {
+  name: string;
+  description?: string;
+  url: string;
+  searchText: string;
+  apis: string[];
+  permissions: string[];
+  packages: string[];
+}
+
+export type ExamplesMetadata = {
+  examples: Example[];
+  allApis: string[];
+  allPermissions: string[];
+  allPackages: string[];
+};
+
+export type KeySelectedObject = Record<string, boolean | undefined>;
+
+export interface PostFrontmatter {
+  title: string;
+  description?: string;
+  date: Date;
+  authors: { name: string; github: string }[];
+}
+
+export interface Post
+  extends Omit<ContentData, 'frontmatter'>, Omit<PostFrontmatter, 'date'> {
+  date: Date;
+}

docs/analytics.md

@@ -0,0 +1 @@
+<!--@include: ../packages/analytics/README.md-->

docs/api/cli/wxt-build.md

@@ -0,0 +1,7 @@
+# `wxt build`
+
+<script setup>
+import { data } from '../../.vitepress/loaders/cli.data.ts'
+</script>
+
+<div class="language-sh vp-adaptive-theme active"><pre class="shiki shiki-themes github-light github-dark vp-code"><code>{{ data.build }}</code></pre></div>

docs/api/cli/wxt-clean.md

@@ -0,0 +1,7 @@
+# `wxt clean`
+
+<script setup>
+import { data } from '../../.vitepress/loaders/cli.data.ts'
+</script>
+
+<div class="language-sh vp-adaptive-theme active"><pre class="shiki shiki-themes github-light github-dark vp-code"><code>{{ data.clean }}</code></pre></div>

docs/api/cli/wxt-init.md

@@ -0,0 +1,7 @@
+# `wxt init`
+
+<script setup>
+import { data } from '../../.vitepress/loaders/cli.data.ts'
+</script>
+
+<div class="language-sh vp-adaptive-theme active"><pre class="shiki shiki-themes github-light github-dark vp-code"><code>{{ data.init }}</code></pre></div>

docs/api/cli/wxt-prepare.md

@@ -0,0 +1,7 @@
+# `wxt prepare`
+
+<script setup>
+import { data } from '../../.vitepress/loaders/cli.data.ts'
+</script>
+
+<div class="language-sh vp-adaptive-theme active"><pre class="shiki shiki-themes github-light github-dark vp-code"><code>{{ data.prepare }}</code></pre></div>

docs/api/cli/wxt-submit-init.md

@@ -0,0 +1,9 @@
+# `wxt submit init`
+
+> Alias for [`publish-browser-extension`](https://www.npmjs.com/package/publish-browser-extension)
+
+<script setup>
+import { data } from '../../.vitepress/loaders/cli.data.ts'
+</script>
+
+<div class="language-sh vp-adaptive-theme active"><pre class="shiki shiki-themes github-light github-dark vp-code"><code>{{ data.submitInit }}</code></pre></div>

docs/api/cli/wxt-submit.md

@@ -0,0 +1,9 @@
+# `wxt submit`
+
+> Alias for [`publish-browser-extension`](https://www.npmjs.com/package/publish-browser-extension)
+
+<script setup>
+import { data } from '../../.vitepress/loaders/cli.data.ts'
+</script>
+
+<div class="language-sh vp-adaptive-theme active"><pre class="shiki shiki-themes github-light github-dark vp-code"><code>{{ data.submit }}</code></pre></div>

docs/api/cli/wxt-zip.md

@@ -0,0 +1,7 @@
+# `wxt zip`
+
+<script setup>
+import { data } from '../../.vitepress/loaders/cli.data.ts'
+</script>
+
+<div class="language-sh vp-adaptive-theme active"><pre class="shiki shiki-themes github-light github-dark vp-code"><code>{{ data.zip }}</code></pre></div>

docs/api/cli/wxt.md

@@ -0,0 +1,7 @@
+# `wxt`
+
+<script setup>
+import { data } from '../../.vitepress/loaders/cli.data.ts'
+</script>
+
+<div class="language-sh vp-adaptive-theme active"><pre class="shiki shiki-themes github-light github-dark vp-code"><code>{{ data.wxt }}</code></pre></div>

docs/assets/extension-showcase.yml

@@ -0,0 +1,533 @@
+# Add extension entries to end of the list. On the website, extensions will be sorted by a combination of users and rating.
+#
+# Change the commit message or PR title to:
+#
+# > "docs: Added "[extension name]" to showcase"
+#
+# Use:
+#
+# - `chromeId` for the Chrome Web Store listing,
+# - `firefoxSlug` for Firefox Add-ons (slug from https://addons.mozilla.org/firefox/addon/{slug}/),
+# - `edgeId` for the Edge Add-ons listing (ID from https://microsoftedge.microsoft.com/addons/detail/{slug}/{id})
+#
+# You may include one or more of these fields for your extension.
+
+- # Anylang Translator
+  chromeId: injdenmpjncknciccmjjmjlgbmnkince
+  firefoxSlug: anylang-translator
+
+- # GitHub: Better Line Counts
+  chromeId: ocfdgncpifmegplaglcnglhioflaimkd
+  firefoxSlug: github-better-line-counts
+
+- # Anime Skip Player
+  chromeId: mgmdkjcljneegjfajchedjpdhbadklcf
+  firefoxSlug: anime-skip
+
+- # UltraWideo
+  chromeId: bfbnagnphiehemkdgmmficmjfddgfhpl
+  firefoxSlug: ultrawideo
+
+- # StayFree - Website Blocker & Web Analytics
+  chromeId: elfaihghhjjoknimpccccmkioofjjfkf
+  firefoxSlug: stayfree
+  edgeId: aghmglalnfmjbipodadgbgpakneabgnp
+
+- # Doozy: Ai Made Easy
+  chromeId: okifoaikfmpfcamplcfjkpdnhfodpkil
+
+- # tl;dv - Record, Transcribe & ChatGPT for Google Meet
+  chromeId: lknmjhcajhfbbglglccadlfdjbaiifig
+
+- # Youtube中文配音
+  chromeId: oglffgiaiekgeicdgkdlnlkhliajdlja
+
+- # PreMiD
+  chromeId: agjnjboanicjcpenljmaaigopkgdnihi
+
+- # Markdown Sticky Notes
+  chromeId: aiakblgmlabokilgljkglggnpflljdgp
+  firefoxSlug: markdown-sticky-notes
+
+- # DocVersionRedirector
+  chromeId: nomnkbngkijpffepcgbbofhcnafpkiep
+
+- # Plex Skipper
+  chromeId: ceicccfeikoipigeghddpocceifjelph
+  firefoxSlug: plex-skipper
+
+- # GitHub Custom Notifier
+  chromeId: aelkipgppclpfimeamgmlonimflbhlgf
+  firefoxSlug: github-custom-notifier
+
+- # Fluent Read
+  chromeId: djnlaiohfaaifbibleebjggkghlmcpcj
+
+- # Facebook Video Controls
+  chromeId: nhclljcpfmmaiojbhhnkpjcfmacfcian
+  firefoxSlug: facebook-video-controls
+
+- # ElemSnap - Quick capture of webpage elements and conversion to images,
+  chromeId: mblkhbaakhbhiimkbcnmeciblfhmafna
+
+- # MS Edge TTS (Text to Speech)
+  chromeId: oajalfneblkfiejoadecnmodfpnaeblh
+  firefoxSlug: ms-edge-tts-text-to-speech
+
+- # YTBlock - Block any content from YouTube™
+  chromeId: nedcanggplmbbgmlpcjiafgjcpdimpea
+
+- # demo.fun - Interactive product demos that convert
+  chromeId: oadbjpccljkplmhnjekgjamejnbadlne
+
+- # SmartEReply: Elevate Your LinkedIn™ Engagement with AI 🚀📈
+  chromeId: iopdafdcollfgaoffingmahpffckmjni
+
+- # WorkFlowy MultiFlow
+  chromeId: khjdmjcmpolknpccmaaipmidphjokhdf
+
+- # 香草布丁🌿🍮- https://github.com/Xdy1579883916/vanilla-pudding
+  chromeId: fencadnndhdeggodopebjgdfdlhcimfk
+
+- # MaxFocus: Link Preview
+  chromeId: bnacincmbaknlbegecpioobkfgejlojp
+  firefoxSlug: maxfocus-link-preview
+
+- # 汇率转换-中文版本
+  chromeId: bcpgdpedphodjcjlminjbdeejccjbimp
+
+- # Currency Converter Plus
+  chromeId: loeilaonggnalkaiiaepbegccilkmjjp
+  firefoxSlug: currency-converter-plus
+
+- # Respond Easy
+  chromeId: npcnninnjghigjfiecefheeibomjpkak
+
+- # mindful - stay focused on your goals
+  chromeId: cfkdcideecefncbglkhneoflfnmhoicc
+
+- # 1Proompt
+  chromeId: lnhejcpclabmbgpiiomjbhalblnnbffg
+
+- # NiceTab - https://github.com/web-dahuyou/NiceTab
+  chromeId: fonflmjnjbkigocpoommgmhljdpljain
+  firefoxSlug: nice-tab-manager
+  edgeId: ompjiaelpibiggcnanhbdblkhfdmkgnl
+
+- # Draftly for LinkedIn
+  chromeId: fcffekbnfcfdemeekijbbmgmkognnmkd
+
+- # YouTube Summarized - Summarize any YouTube video
+  chromeId: nkndldfehcidpejfkokbeghpnlbppdmo
+
+- # 社媒助手 - https://github.com/iszhouhua/social-media-copilot
+  chromeId: dbichmdlbjdeplpkhcejgkakobjbjalc
+
+- # Dofollow Links for SEO
+  chromeId: opepfpjeogkbgeigkbepobceinnfmjdd
+
+- # ChatGPT Writer: Use AI on Any Site (GPT-4o, Claude, Gemini, and More)
+  chromeId: pdnenlnelpdomajfejgapbdpmjkfpjkp
+
+- # discord message translator
+  chromeId: jobnhifpphkgoelnhnopgkdhbdkiadmj
+
+- # Habit Tracker app widget for daily habit tracking
+  chromeId: ncokhechhpjgjonhjnlaneglmdkfkcbj
+
+- # Catppuccin for GitHub File Explorer Icons
+  chromeId: lnjaiaapbakfhlbjenjkhffcdpoompki
+  firefoxSlug: catppuccin-web-file-icons
+
+- # WebChat: Chat with anyone on any website
+  chromeId: cpaedhbidlpnbdfegakhiamfpndhjpgf
+
+- # YouTube Auto HD + FPS
+  chromeId: fcphghnknhkimeagdglkljinmpbagone
+  firefoxSlug: youtube-auto-hd-fps
+
+- # YouTube Auto Feed
+  chromeId: jcdebdlnakhdinkindpogcehnhggbfad
+  firefoxSlug: youtube-auto-feed
+
+- # YouTube Like-Dislike Shortcut
+  chromeId: fdkpkpelkkdkjhpacficichkfifijipc
+  firefoxSlug: youtube-like-dislike-shortcut
+
+- # Twitch Channel Points Bonus Collector
+  chromeId: kbbdnbaghpcjpdhbjbccadodjejlkkgg
+  firefoxSlug: twitch-cp-bonus-collector
+
+- # Skillshare Player Control
+  chromeId: agbhgcomfpcfboebbfmefbicfkpnlfeg
+  firefoxSlug: skillshare-player-control
+
+- # MultiViewer Companion
+  chromeId: lpomjgbicdemjkgmbnkjncgdebogkhlb
+  firefoxSlug: multiviewer-companion
+
+- # Sync Watch - Watch videos together on any site
+  chromeId: ggiafipgeeaaahnjamgpjcgkdpanhddg
+  firefoxSlug: syncwatch
+
+- # Keyword Rank Checker
+  chromeId: nmldnjcblcihmegipecakhmnieiofmgl
+  firefoxSlug: keyword-rank-checker-sa
+
+- # YouTube Simple View - Hide distractions & more
+  chromeId: gppllamhaciichleihemgilcpledblpn
+  firefoxSlug: youtube-simple-view
+
+- # Propbar - Property Data Enhancer
+  chromeId: pccbghdfdnnkkbcdcibchpbffdgednkf
+
+- # Text Search Pro - Search by case and whole-word match!
+  chromeId: lfknakglefggmdkjdfhhofkjnnolffkh
+  firefoxSlug: text-search-pro-ext
+
+- # Invoice Generator
+  chromeId: mbenhbocjckkbaojacmaepiameldglij
+  firefoxSlug: quick-invoice-generator
+
+- # Monthly Bill Tracker
+  chromeId: phlfhkmdofajnbhgmbmjkbkdgppgoppb
+
+- # Wandpen - Instantly improve your writing with AI
+  chromeId: macmkmchfoclhpbncclinhjflmdkaoom
+
+- # YouTube Hider - Remove Comments By Keywords, Usernames & Tools
+  chromeId: lhmgechokhmdekdpgkkemoeecelcaonm
+
+- # QA Compass - Record standardized bug reports easily
+  chromeId: imgheieooppmahcgniieddodaliodeeg
+
+- # aesthetic Notion, styled
+  chromeId: npgghjedpchajflknnbngajkjkdhncdo
+
+- # Eye Dropper
+  chromeId: hmdcmlfkchdmnmnmheododdhjedfccka
+  firefoxSlug: eye_dropper
+
+- # Cursorful - Screen Recorder with Auto Zoom
+  chromeId: eihpmapodnppeemkhkbhikmggfojdkjd
+
+- # Show IP – Live View of Website IPs for Developers
+  chromeId: hjjkgbibknbahijglkffklflidncplkn
+
+- # Strong Password Generator
+  chromeId: ilbikcehnpkmldojkcmlldkoelofnbde
+  firefoxSlug: strongpasswordgenerator
+
+- # ZenGram: Mindful Instagram, Your Way
+  chromeId: ocllfkhcdopiafndigclebelbecaiocp
+
+- # Blync: Preview Links, Selection Search, AI Assistant
+  chromeId: odffpjnpocjfcaclnenaaaddghkgijdb
+
+- # HTML to Markdown - Convert webpages to markdown
+  chromeId: kofbbilhmnkcmibjbioafflgmpkbnmme
+
+- # Walmart WFS Profit Calculator
+  chromeId: boecmgggeigllcdocgioijmleimjbfkg
+  firefoxSlug: walmart-wfs-profit-calculator
+
+- # Youtube Live Chat Fullscreen
+  chromeId: dlnjcbkmomenmieechnmgglgcljhoepd
+  firefoxSlug: youtube-live-chat-fullscreen
+
+- # Python Code Runner
+  chromeId: keiealdacakpnbbljlmhfgcebmaadieg
+  firefoxSlug: code-runner-manager
+
+- # Monochromate
+  chromeId: hafcajcllbjnoolpfngclfmmgpikdhlm
+  firefoxSlug: monochromate
+
+- # AliasVault - Open-Source Password & (Email) Alias Manager
+  chromeId: bmoggiinmnodjphdjnmpcnlleamkfedj
+
+- # SnapThePrice: AI-Powered Real-time Lowest Price Finder
+  chromeId: hlnhhamckimoaiekbglafiebkfimhapb
+
+- # radiofrance - news & broadcasts (French), music (international)
+  chromeId: gdjampjdgjmbifnhldgcnccdjkcoicmg
+
+- # Blens - Time Tracker and AI Insight
+  chromeId: jlnhphlghikichhgbnkepenehbmloenb
+  firefoxSlug: blens-timetracker-ai-insight
+
+- # Always Light Mode - Setting website always in light mode
+  chromeId: njnammmpdodmfkodnfpammnpdcbhnlcm
+
+- # DesignPicker - Color Picker & Font Detector
+  chromeId: lblmfclcfniabobmamfkdogcgdagbhhb
+  firefoxSlug: design-colorpicker-fontdetect
+
+- # Web to PDF
+  chromeId: pamnlaoeobcmhkliljfaofekeddpmfoh
+  firefoxSlug: export-web-to-pdf
+
+- # Online CSV Viewer
+  chromeId: jmbcbeepjfenihlocplnbmbhimcoooka
+  firefoxSlug: csv-viewer
+
+- # YouTube Video Transcript
+  chromeId: nkjcoophmpcmmgadnljnlpbpfdfacgbo
+  firefoxSlug: youtube-transcript-copy
+
+- # NetSuite Record Scripts
+  chromeId: lcaieahkjgeggeiihblhcjbbjlppgieh
+  firefoxSlug: netsuite-scripts-manager
+
+- # VueTracker
+  chromeId: gmocfknjllodfiomnljmaehcplnekhlo
+
+- # CanCopy - A web extension that allow you to copy any content from website
+  chromeId: ggcfemmoabhhelfkhknhbnkmeahloiod
+
+- # Read Frog
+  chromeId: modkelfkcfjpgbfmnbnllalkiogfofhb
+  firefoxSlug: read-frog-open-ai-translator
+
+- # Bilibili Feed History Helper
+  chromeId: npfopljnjbamegincfjelhjhnonnjloo
+
+- # NZBDonkey - The ultimate NZB file download tool
+  chromeId: edkhpdceeinkcacjdgebjehipmnbomce
+
+- # WeChat Markdown Editor(微信 Markdown 编辑器)
+  chromeId: cckggnbnimdbbpmdinkkgbbncopbloob
+
+- # Tab Grab
+  chromeId: jcblcjolcojmfopefcighfmkkefbaofg
+  firefoxSlug: tab-grab
+
+- # BrowserLens - https://browserlens.com/
+  chromeId: eehmoikadcijkapfjocnhjclpbaindlb
+  firefoxSlug: browserlens
+
+- # Epic Games Library Extension
+  chromeId: hfhellofkjebbchcdffmicekjdomkcmc
+  firefoxSlug: epic-games-library-extension
+
+- # Zen Analytics Pixel Tracker - zapt.web.app
+  chromeId: gknigcbhlammoakmmdddkblknanpjiac
+
+- # Crypto Pulse - Compose your newtab with nature images, widgets & realtime Crypto Price & Bitcoin RSS.
+  chromeId: cnklededohhcbmjjdlbjdkkihkgoggol
+
+- # Youtube Video Scheduler
+  chromeId: miponnamafdenpgjemkknimgjfibicdc
+  firefoxSlug: youtube-video-scheduler
+
+- # Chatslator: Livestream Chat Translator
+  chromeId: nhmbcmalgpkjbomhlhgdicanmkkaajmg
+  firefoxSlug: chatslator
+
+- # 公众号阅读增强器 - https://wxreader.honwhy.wang
+  chromeId: mbamjfdjbcdgpopfnkkmlohadbbnplhm
+
+- # 토탐정
+  chromeId: hannhecbnjnnbbafffmogdlnajpcomek
+  firefoxSlug: 토탐정
+
+- # 2FAS Pass - https://2fas.com/
+  chromeId: ehboaofjncodknjkngdggmpdinhdoijp
+  firefoxSlug: 2fas-pass-browser-extension
+
+- # Quick Prompt - https://github.com/wenyuanw/quick-prompt
+  chromeId: hnjamiaoicaepbkhdoknhhcedjdocpkd
+  firefoxSlug: quick-prompt
+
+- # Add QR Code Generator Icon Back To Address Bar
+  chromeId: kacblhilkacgfnkjfodalohcnllcgmjd
+
+- # Piwik PRO Tracking Helper
+  chromeId: fkbdlogfdjmpfepbbbjcgcfbgbcfcnne
+  firefoxSlug: piwik-pro-tracking-helper
+
+- # PIPX - Take Control of Picture-in-Picture, Automatically
+  chromeId: nkbikckldmljjiiajklecmgmajgapbfl
+
+- # Browsely - AI-powered browser extension
+  chromeId: hgppdobcpkfkmiegekaglonjajeojmdd
+
+- # Filmbudd Pro - Simple, private – and synced ratings and watch notes across all your devices
+  chromeId: ehmoihnjgkdimihkhokkmfjdgomohjgm
+
+- # MultiField CopyCat - Copy, Paste & Autofill Web Forms Instantly
+  chromeId: alglchohmdikgdjhafiicilegegieafa
+
+- # ChatSight - Add Table of Contents to ChatGPT
+  chromeId: aamihahiiogceidpbnfgehacgiecephe
+
+- # BetterCampus (prev. BetterCanvas)
+  chromeId: cndibmoanboadcifjkjbdpjgfedanolh
+  firefoxSlug: better-canvas
+
+- # Leetcode Fonts - Change fonts in leetcode effortlessly
+  chromeId: hinfimgacobnellbncbcpdlpaapcofaa
+
+- # TranslateManga - Manga Translator & Manga Tracker
+  chromeId: kbkbfefhhabpkibojinapkkgciiacggg
+
+- # SiteData - Free Website Traffic Checker & Reverse AdSense Tool
+  chromeId: emeakbgdecgmdjgegnejpppcnkcnoaen
+  firefoxSlug: sitedata
+
+- # Livestream Chat Reader - Text-to-Speech for YouTube/Twitch chat
+  chromeId: gpnckbhgpnjciklpoehkmligeaebigaa
+
+- # ChatGPT Token Counter - Count tokens in real time on chatgpt conversation
+  chromeId: fjlalaedpfcojcfpkgkglbjjbbkofgnl
+  firefoxSlug: chatgpt-token-counter
+
+- # LinuxDo Scripts - 为 linux.do 用户提供了一些增强功能
+  chromeId: fbgblmjbeebanackldpbmpacppflgmlj
+  firefoxSlug: linux_do-scripts
+
+- # Zen Virtual Piano - https://zen-piano.web.app/
+  chromeId: dfacnjidgbagicaekenjgclfnhdnjjdi
+
+- # Crypto Pulse price tracker - https://get-crypto-pulse.web.app/
+  chromeId: naeibcegmgpofimedkmfgjgphfhfhlab
+
+- # Redirect Web - Automatically redirect pages or open them in another app
+  chromeId: ffglckbhfbfmdkefdmjbhpnffkcmlhdh
+
+- # Capture It - Capture & Edit Screenshots
+  chromeId: eglpfhbhmelampoihamjomgkeobgdofl
+
+- # Teams Chat Exporter
+  chromeId: jmghclbfbbapimhbgnpffbimphlpolnm
+  firefoxSlug: teams-chat-exporter
+  edgeId: phlomfiieaggnbfpacmjmidcjdlaiplp
+
+- # Lofi BGM Player - Free lofi focus music for work & study
+  chromeId: jdcppdokgfbnhiacbeplahgnciahnhck
+  firefoxSlug: lofi-bgm-player
+
+- # Margin - Annotate and highlight any webpage, with your notes saved to the decentralized AT Protocol.
+  chromeId: cgpmbiiagnehkikhcbnhiagfomajncpa
+
+- # KeyFloat - Floating multilingual keyboard with native key mappings, drag, dark mode, sounds, and dynamic layouts for macOS & Windows
+  chromeId: mfjdonmgmgcijagclnkfhmjiblbfjaid
+
+- # Glossy New Tab - Say Goodbye to Boring Tabs with live wallpapers
+  chromeId: dhiekgdaipindoapjmcnpompdknjeijf
+  firefoxSlug: glossy-new-tab
+
+- # All API Hub – AI Relay & New API Manager - https://github.com/qixing-jk/all-api-hub
+  chromeId: lapnciffpekdengooeolaienkeoilfeo
+  firefoxSlug: all-api-hub
+
+- # Scrape Similar - Extract data from websites into spreadsheets - https://github.com/zizzfizzix/scrape-similar
+  chromeId: bhgobenflkkhfcgkikejaaejenoddcmo
+
+- # isTrust - https://github.com/Internet-Society-Belgium/isTrust/
+  chromeId: kinlknncggaihnhdcalijdmpbhbflalm
+
+- # Dymo
+  chromeId: ojpakgiekphppgkcdihbjpafobhnhlkp
+
+- # Extension Rank Checker - Extension Ranker
+  chromeId: pmgehhllikbjmadpenhabejhpemplhmd
+  firefoxSlug: rank-checker
+
+- # PlayFaster - Enhanced playback speed control for online videos and audio
+  chromeId: fppcbkhpahkbgijkdcpjgjmhpfbmfiih
+  firefoxSlug: playfaster
+
+- # LatTab - Learn Latin With Every New Tab
+  chromeId: eiocjaocpmackhbaffoejkcmnfbdpgpj
+  firefoxSlug: lattab-learn-latin-new-tabs
+
+- # Vim What? - Interactive Vim command reference
+  chromeId: ngbehgnlcdjkbnihgpkgdangbhemidge
+  firefoxSlug: vim-what
+
+- # FRED - Fraud Recognition Easy Detection
+  chromeId: bjdbcabacnlmbpcmiapcdfancfgcakfn
+  firefoxSlug: fred
+
+- # Clear Wisdom - Gems of wisdom from James Clear's 3-2-1 newsletter
+  chromeId: jijfmgoijddfmlcdghopbkdpelbpmjdm
+  firefoxSlug: clear-wisdom
+
+- # Soundcloud Enhanced Pro
+  chromeId: ggplcohodggmdfpopelnpplhgfjclomi
+
+- # AlarmBot: ULTIMATE Web Monitoring & Smart Price Alerts
+  chromeId: mpckalcodookackleecihhnngdibelif
+
+- # TF2 Trader - TF2 & Steam Trading Extension - https://github.com/offish/tf2-trader
+  chromeId: gmicpekfpbikhibodgokfpghadkclhoe
+
+- # Mimik
+  chromeId: jmfohdaflahliammccpiadmkcibohgha
+  firefoxSlug: mimik
+
+- # Modrinth Extras - https://github.com/creeperkatze/modrinth-extras
+  chromeId: ajmkilipadfpaefpcjfgnkejalmhdlcj
+  firefoxSlug: modrinth-extras
+
+- # Pi-hole In One - https://github.com/creeperkatze/pihole-in-one
+  chromeId: gaaobidjebianpcngcfpkniaocibidhe
+  firefoxSlug: pihole-in-one
+
+- # QIE Wallet – Non-Custodial Multi-Chain Crypto Wallet
+  chromeId: oljchdcgmibnjbbopolafbjncfhdacjb
+
+- # Headstart – Supercharge your browsing efficiency https://useheadstart.app/
+  chromeId: fhhldbfombjdnjnpeojjohloohmbanda
+
+- # Redmine Time Tracking
+  chromeId: ldcanhhkffokndenejhafhlkapflgcjg
+  firefoxSlug: redmine-time-tracking
+
+- # Telsia: Eye Strain Reduction
+  chromeId: iakkmikmbknfcffhalijnhijblikoldc
+  firefoxSlug: telsia-eye-strain-reduction
+
+- # Sound Booster & Equalizer
+  chromeId: podnfipggfpfcpglhjebcefinglohbhn
+
+- # Link Later
+  chromeId: gpehbbegbcpjmipphokcmfhkchhcpfam
+
+- # Google Cloud Skills Boost - Helper
+  chromeId: lmbhjioadhcoebhgapaidogodllonbgg
+  firefoxSlug: cloud-skills-boost-helper
+
+- # Property Track - https://www.propertytrack.co
+  chromeId: ahknifalnhmbanoclebllcolcdomfdop
+  firefoxSlug: propertytrack
+
+- # WageSlav3
+  chromeId: anhkcmapjhiiofpcgglfljphdgppilof
+
+- # LinkedIn Games Solver
+  chromeId: jnhgapnkejaijibcdhcldhdfikjmdaph
+  firefoxSlug: linkedin-games-solver-addon
+
+- # Hayami: Anime comments & discussions
+  chromeId: nhkggpiaeaeeeimohfpchnjobbamfcbg
+  firefoxSlug: hayami
+
+- # CopyApes Assistant
+  chromeId: affmjifigldmicnbgpghddaneomejmfo
+
+- # Leetcode Enhancer
+  chromeId: cpoclfijojgjiafnlgnhjalkaiabcjch
+
+- # Adaptive Tab Bar Colour
+  firefoxSlug: adaptive-tab-bar-colour
+
+- #ArcPort - Tab Checkpoint
+  chromeId: kajmnfhpmkimleehomeioondgfcjjnbp
+
+- #ArcPort - Tab Rebrand
+  chromeId: pgmohcikgaeddapienpncpbiklbmfkgp
+
+- #MindSnap
+  chromeId: mdcpckfcphpicfpiopfcpeambjknjabl

docs/auto-icons.md

@@ -0,0 +1 @@
+<!--@include: ../packages/auto-icons/README.md-->

docs/blog.md

@@ -0,0 +1,9 @@
+---
+layout: page
+---
+
+<script lang="ts" setup>
+import BlogHome from './.vitepress/components/BlogHome.vue';
+</script>
+
+<BlogHome />

docs/blog/.drafts/2024-10-19-real-world-messaging.md

@@ -0,0 +1,12 @@
+---
+layout: blog
+title: Real World Messaging
+description: |
+  The extension messaging APIs are difficult to learn. Let's go beyond the simple examples from Chrome and Firefox's documentation to build our own simple messaging system from scratch.
+authors:
+  - name: Aaron Klinker
+    github: aklinker1
+date: 2024-10-20T04:54:23.601Z
+---
+
+Test content **bold** _italic_

docs/blog/2024-12-06-using-imports-module.md

@@ -0,0 +1,76 @@
+---
+layout: blog
+title: Introducing <code>#imports</code>
+description: Learn how WXT's new <code>#imports</code> module works and how to use it.
+authors:
+  - name: Aaron Klinker
+    github: aklinker1
+date: 2024-12-06T14:39:00.000Z
+---
+
+WXT v0.20 introduced a new way of manually importing its APIs: **the `#imports` module**. This module was introduced to simplify import statements and provide more visibility into all the APIs WXT provides.
+
+<!-- prettier-ignore -->
+```ts
+import { browser } from 'wxt/browser'; // [!code --]
+import { createShadowRootUi } from 'wxt/utils/content-script-ui/shadow-root'; // [!code --]
+import { defineContentScript } from 'wxt/utils/define-content-script'; // [!code --]
+import { injectScript } from 'wxt/utils/inject-script'; // [!code --]
+import { // [!code ++]
+  browser, createShadowRootUi, defineContentScript, injectScript // [!code ++]
+} from '#imports'; // [!code ++]
+```
+
+The `#imports` module is considered a "virtual module", because the file doesn't actually exist. At build-time, imports are split into individual statements for each API:
+
+:::code-group
+
+```ts [What you write]
+import { defineContentScript, injectScript } from '#imports';
+```
+
+```ts [What the bundler sees]
+import { defineContentScript } from 'wxt/utils/define-content-script';
+import { injectScript } from 'wxt/utils/inject-script';
+```
+
+:::
+
+Think of `#imports` as a convenient way to access all of WXT's APIs from one place, without impacting performance or bundle size.
+
+This enables better tree-shaking compared to v0.19 and below.
+
+:::tip Need to lookup the full import path of an API?
+Open up your project's `.wxt/types/imports-module.d.ts` file.
+:::
+
+## Mocking
+
+When writing tests, you might need to mock APIs from the `#imports` module. While mocking these APIs is very easy, it may not be immediately clear how to accomplish it.
+
+Let's look at an example using Vitest. When [configured with `wxt/testing`](/guide/essentials/unit-testing#vitest), Vitest sees the same transformed code as the bundler. That means to mock an API from `#imports`, you need to call `vi.mock` with the real import path, not `#imports`:
+
+```ts
+import { injectScript } from '#imports';
+import { vi } from 'vitest';
+
+vi.mock('wxt/utils/inject-script')
+const injectScriptMock = vi.mocked(injectScript);
+
+injectScriptMock.mockReturnValueOnce(...);
+```
+
+## Conclusion
+
+You don't have to use `#imports` if you don't like - you can continue importing APIs from their submodules. However, using `#imports` is the recommended approach moving forwards.
+
+- As more APIs are added, you won't have to memorize additional import paths.
+- If breaking changes are made to import paths in future major versions, `#imports` won't break.
+
+Happy Coding 😄
+
+> P.S. Yes, this is exactly how [Nuxt's `#imports`](https://nuxt.com/docs/guide/concepts/auto-imports#explicit-imports) works! We use the exact same library, [`unimport`](https://github.com/unjs/unimport).
+
+---
+
+[Discuss this blog post on Github](https://github.com/wxt-dev/wxt/discussions/1543).

docs/entrypoints/background.md

@@ -1,47 +0,0 @@
-# Background
-
-[Chrome Docs](https://developer.chrome.com/docs/extensions/mv3/manifest/background/) • [Firefox Docs](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/background)
-
-For MV2, the background is added as a script to the background page. For MV3, the background becomes a service worker.
-
-## Filenames
-
-<EntrypointPatterns
-  :patterns="[
-    ['background.[jt]s', 'background.js'],
-    ['background/index.[jt]s', 'background.js'],
-  ]"
-/>
-
-## Definition
-
-:::warning
-The main function of the background **_CANNOT BE ASYNC_**. Event listeners must be added synchronously on background startup. If your main function returns a promise, WXT will log an error.
-:::
-
-```ts
-export default defineBackground(() => {
-  // Executed when background is loaded
-});
-```
-
-or
-
-```ts
-export default defineBackground({
-  // Set manifest options
-  persistent: undefined | true | false,
-  type: undefined | 'module',
-
-  // Set include/exclude if the background should be removed from some builds
-  include: undefined | string[],
-  exclude: undefined | string[],
-
-  // Executed when background is loaded
-  main() {
-    // ...
-  },
-});
-```
-
-> All manifest options default to `undefined`.

docs/entrypoints/bookmarks.md

@@ -1,31 +0,0 @@
-# Bookmarks
-
-[Chrome Docs](https://developer.chrome.com/docs/extensions/mv3/override/) • [Firefox Docs](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/chrome_url_overrides)
-
-## Filenames
-
-<EntrypointPatterns
-  :patterns="[
-    ['bookmarks.html', 'bookmarks.html'],
-    ['bookmarks/index.html', 'bookmarks.html'],
-  ]"
-/>
-
-## Definition
-
-```html
-<!doctype html>
-<html lang="en">
-  <head>
-    <meta charset="UTF-8" />
-    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-    <title>Title</title>
-    <!-- Set include/exclude if the page should be removed from some builds -->
-    <meta name="manifest.include" content="['chrome', ...]" />
-    <meta name="manifest.exclude" content="['chrome', ...]" />
-  </head>
-  <body>
-    <!-- ... -->
-  </body>
-</html>
-```

docs/entrypoints/content-scripts.md

@@ -1,107 +0,0 @@
-# Content Scripts
-
-[Chrome Docs](https://developer.chrome.com/docs/extensions/mv3/content_scripts/) • [Firefox Docs](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Content_scripts)
-
-When creating content script entrypoints, they are automatically included in the `manifest.json` along with any CSS files they import.
-
-## Filenames
-
-<EntrypointPatterns
-  :patterns="[
-    ['content.[jt]sx?', 'content-scripts/content.js'],
-    ['content/index.[jt]sx?', 'content-scripts/content.js'],
-    ['<name>.content.[jt]sx?', 'content-scripts/<name>.js'],
-    ['<name>.content/index.[jt]sx?', 'content-scripts/<name>.js'],
-  ]"
-/>
-
-## Definition
-
-```ts
-export default defineContentScript({
-  // Set manifest options
-  matches: string[],
-  excludeMatches: undefined | [],
-  includeGlobs: undefined | [],
-  excludeGlobs: undefined | [],
-  allFrames: undefined | [],
-  runAt: undefined | 'document_start' | 'document_end' | 'document_idle',
-  matchAboutBlank: undefined | true | false,
-  matchOriginAsFallback: undefined | true | false,
-  world: undefined | 'ISOLATED' | 'MAIN',
-
-  // Set include/exclude if the background should be removed from some builds
-  include: undefined | string[],
-  exclude: undefined | string[],
-
-  // Configure how CSS is injected onto the page
-  cssInjectionMode: undefined | "manifest" | "manual" | "ui",
-
-  // Configure how/when content script will be registered
-  registration: undefined | "manifest" | "runtime",
-
-  main(ctx: ContentScriptContext) {
-    // Executed when content script is loaded
-  },
-});
-```
-
-> All manifest options default to `undefined`.
-
-When defining multiple content scripts, content script entrypoints that have the same set of options will be merged into a single `content_script` item in the manifest.
-
-## CSS
-
-To include CSS with your content script, import the CSS file at the top of your entrypoint.
-
-```
-
-<srcDir>/
-└─ entrypoints/
-   └─ overlay.content/
-      ├─ index.ts
-      └─ style.css
-```
-
-```ts
-// entrypoints/overlay.content/index.ts
-import './style.css';
-
-export default defineContentScript({
-  matches: ['*://google.com/*', '*://duckduckgo.com/*'],
-
-  main(ctx) {
-    // ...
-  },
-});
-```
-
-Any styles imported in your content script will be added to that content script's `css` array in your `manifest.json`:
-
-```json
-// .output/chrome-mv3/manifest.json
-{
-  "content_scripts": [
-    {
-      "matches": ["*://google.com/*", "*://duckduckgo.com/*"],
-      "js": ["content-scripts/overlay.js"],
-      "css": ["content-scripts/overlay.css"]
-    }
-  ]
-}
-```
-
-To disable this behavior, set `cssInjectionMode` to `"manual"` or `"ui"`.
-
-```ts
-export default defineContentScript({
-  matches: ['*://google.com/*', '*://duckduckgo.com/*'],
-  cssInjectionMode: 'manual',
-
-  main(ctx) {
-    // ...
-  },
-});
-```
-
-See [Content Script UI](/guide/content-script-ui) for more info on creating UIs and including CSS in content scripts.

docs/entrypoints/css.md

@@ -1,44 +0,0 @@
-# CSS
-
-WXT can build CSS entrypoints individually. CSS entrypoints are always unlisted.
-
-See [Content Script CSS](/entrypoints/content-scripts#css) documentation for the recommended approach to include CSS with a content script.
-
-:::info
-If the recommended approach doesn't work for your use case, you can use any of the filename patterns below to build the styles separate from the JS and use the [`transformManifest` hook](/api/wxt/interfaces/InlineConfig#transformmanifest) to manually add your CSS file to the manifest.
-:::
-
-## Filenames
-
-<EntrypointPatterns
-  :patterns="[
-    ['<name>.(css|scss|sass|less|styl|stylus)', '<name>.css'],
-    ['<name>/index.(css|scss|sass|less|styl|stylus)', '<name>.css'],
-    ['content.(css|scss|sass|less|styl|stylus)', 'content-scripts/content.css'],
-    ['content/index.(css|scss|sass|less|styl|stylus)', 'content-scripts/content.css'],
-    ['<name>.content.(css|scss|sass|less|styl|stylus)', 'content-scripts/<name>.css'],
-    ['<name>.content/index.(css|scss|sass|less|styl|stylus)', 'content-scripts/<name>.css'],
-  ]"
-/>
-
-## Definition
-
-```css
-body {
-  /* Plain CSS file */
-}
-```
-
-Follow Vite's guide to setup a preprocessor: https://vitejs.dev/guide/features.html#css-pre-processors
-
-```sh
-pnpm i sass
-```
-
-```scss
-body {
-  h1 {
-    /* ...*/
-  }
-}
-```

docs/entrypoints/devtools.md

@@ -1,40 +0,0 @@
-# Devtools
-
-[Chrome Docs](https://developer.chrome.com/docs/extensions/mv3/devtools/) • [Firefox Docs](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/devtools_page)
-
-## Filenames
-
-<EntrypointPatterns
-  :patterns="[
-    ['devtools.html', 'devtools.html'],
-    ['devtools/index.html', 'devtools.html'],
-  ]"
-/>
-
-## Definition
-
-```html
-<!doctype html>
-<html lang="en">
-  <head>
-    <meta charset="UTF-8" />
-    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-    <!-- Set include/exclude if the page should be removed from some builds -->
-    <meta name="manifest.include" content="['chrome', ...]" />
-    <meta name="manifest.exclude" content="['chrome', ...]" />
-  </head>
-  <body>
-    <!-- ... -->
-  </body>
-</html>
-```
-
-## Adding UI Elements
-
-Chrome extensions allow you to add panels and side panes to the devtools window.
-
-![DevTools window showing Elements panel and Styles sidebar pane.](https://developer.chrome.com/static/docs/extensions/how-to/devtools/extend-devtools/image/devtools-window-showing-e-9051f7f0347cd_1920.png)
-
-See the WXT's examples for a full walkthrough of extending the devtools window:
-
-<ExampleList tag="devtools" />

docs/entrypoints/history.md

@@ -1,31 +0,0 @@
-# History
-
-[Chrome Docs](https://developer.chrome.com/docs/extensions/mv3/override/) • [Firefox Docs](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/chrome_url_overrides)
-
-## Filenames
-
-<EntrypointPatterns
-  :patterns="[
-    ['history.html', 'history.html'],
-    ['history/index.html', 'history.html'],
-  ]"
-/>
-
-## Definition
-
-```html
-<!doctype html>
-<html lang="en">
-  <head>
-    <meta charset="UTF-8" />
-    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-    <title>Title</title>
-    <!-- Set include/exclude if the page should be removed from some builds -->
-    <meta name="manifest.include" content="['chrome', ...]" />
-    <meta name="manifest.exclude" content="['chrome', ...]" />
-  </head>
-  <body>
-    <!-- ... -->
-  </body>
-</html>
-```

docs/entrypoints/newtab.md

@@ -1,31 +0,0 @@
-# Newtab
-
-[Chrome Docs](https://developer.chrome.com/docs/extensions/mv3/override/) • [Firefox Docs](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/chrome_url_overrides)
-
-## Filenames
-
-<EntrypointPatterns
-  :patterns="[
-    ['newtab.html', 'newtab.html'],
-    ['newtab/index.html', 'newtab.html'],
-  ]"
-/>
-
-## Definition
-
-```html
-<!doctype html>
-<html lang="en">
-  <head>
-    <meta charset="UTF-8" />
-    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-    <title>Title</title>
-    <!-- Set include/exclude if the page should be removed from some builds -->
-    <meta name="manifest.include" content="['chrome', ...]" />
-    <meta name="manifest.exclude" content="['chrome', ...]" />
-  </head>
-  <body>
-    <!-- ... -->
-  </body>
-</html>
-```

docs/entrypoints/options.md

@@ -1,36 +0,0 @@
-# Options
-
-[Chrome Docs](https://developer.chrome.com/docs/extensions/mv3/options/) • [Firefox Docs](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/options_ui)
-
-## Filenames
-
-<EntrypointPatterns
-  :patterns="[
-    ['options.html', 'options.html'],
-    ['options/index.html', 'options.html'],
-  ]"
-/>
-
-## Definition
-
-```html
-<!doctype html>
-<html lang="en">
-  <head>
-    <meta charset="UTF-8" />
-    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-    <title>Options Title</title>
-    <meta name="manifest.open_in_tab" content="true|false" />
-    <meta name="manifest.chrome_style" content="true|false" />
-    <meta name="manifest.browser_style" content="true|false" />
-    <!-- Set include/exclude if the page should be removed from some builds -->
-    <meta name="manifest.include" content="['chrome', ...]" />
-    <meta name="manifest.exclude" content="['chrome', ...]" />
-  </head>
-  <body>
-    <!-- ... -->
-  </body>
-</html>
-```
-
-> All manifest options default to `undefined` when the `meta` tag is not present.

docs/entrypoints/popup.md

@@ -1,43 +0,0 @@
-# Popup
-
-[Chrome Docs](https://developer.chrome.com/docs/extensions/reference/action/) • [Firefox Docs](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/manifest.json/action)
-
-## Filenames
-
-<EntrypointPatterns
-  :patterns="[
-    ['popup.html', 'popup.html'],
-    ['popup/index.html', 'popup.html'],
-  ]"
-/>
-
-## Definition
-
-```html
-<!doctype html>
-<html lang="en">
-  <head>
-    <meta charset="UTF-8" />
-    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-    <title>Default Popup Title</title>
-    <meta
-      name="manifest.default_icon"
-      content="{
-        16: '/icon-16.png',
-        24: '/icon-24.png',
-        ...
-      }"
-    />
-    <meta name="manifest.type" content="page_action|browser_action" />
-    <meta name="manifest.browser_style" content="true|false" />
-    <!-- Set include/exclude if the page should be removed from some builds -->
-    <meta name="manifest.include" content="['chrome', ...]" />
-    <meta name="manifest.exclude" content="['chrome', ...]" />
-  </head>
-  <body>
-    <!-- ... -->
-  </body>
-</html>
-```
-
-> All manifest options default to `undefined` when the `meta` tag is not present.

docs/entrypoints/sandbox.md

@@ -1,37 +0,0 @@
-# Sandbox
-
-[Chrome Docs](https://developer.chrome.com/docs/extensions/mv3/manifest/sandbox/)
-
-:::tip Chromium Only
-Firefox does not support sandboxed pages.
-:::
-
-## Filenames
-
-<EntrypointPatterns
-  :patterns="[
-    ['sandbox.html', 'sandbox.html'],
-    ['sandbox/index.html', 'sandbox.html'],
-    ['<name>.sandbox.html', '<name>.html` '],
-    ['<name>.sandbox/index.html', '<name>.html` '],
-  ]"
-/>
-
-## Definition
-
-```html
-<!doctype html>
-<html lang="en">
-  <head>
-    <meta charset="UTF-8" />
-    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-    <title>Title</title>
-    <!-- Set include/exclude if the page should be removed from some builds -->
-    <meta name="manifest.include" content="['chrome', ...]" />
-    <meta name="manifest.exclude" content="['chrome', ...]" />
-  </head>
-  <body>
-    <!-- ... -->
-  </body>
-</html>
-```

docs/entrypoints/sidepanel.md

@@ -1,49 +0,0 @@
-# Side Panel
-
-[Chrome Docs](https://developer.chrome.com/docs/extensions/reference/sidePanel/) • [Firefox Docs](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/user_interface/Sidebars)
-
-In Chrome, side panels use the "side_panel" API, while Firefox uses the "sidebar_action" API.
-
-:::warning
-Chrome added support for sidepanels in Manifest V3, they are not available in Manifest V2.
-:::
-
-## Filenames
-
-<EntrypointPatterns
-  :patterns="[
-    ['sidepanel.html', 'sidepanel.html'],
-    ['sidepanel/index.html', 'sidepanel.html'],
-    ['<name>.sidepanel.html', '<name>.html` '],
-    ['<name>.sidepanel/index.html', '<name>.html` '],
-  ]"
-/>
-
-## Definition
-
-```html
-<!doctype html>
-<html lang="en">
-  <head>
-    <meta charset="UTF-8" />
-    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-    <title>Default Side Panel Title</title>
-    <meta
-      name="manifest.default_icon"
-      content="{
-        16: '/icon-16.png',
-        24: '/icon-24.png',
-        ...
-      }"
-    />
-    <meta name="manifest.open_at_install" content="true|false" />
-    <meta name="manifest.browser_style" content="true|false" />
-    <!-- Set include/exclude if the page should be removed from some builds -->
-    <meta name="manifest.include" content="['chrome', ...]" />
-    <meta name="manifest.exclude" content="['chrome', ...]" />
-  </head>
-  <body>
-    <!-- ... -->
-  </body>
-</html>
-```

docs/entrypoints/unlisted-pages.md

@@ -1,49 +0,0 @@
-# Unlisted Pages
-
-HTML pages that are bundled and shipped with the extension, but are not included in the manifest.
-
-If you plan on using the page in an iframe, don't forget to add the page to [`web_accessible_resources`](https://developer.chrome.com/docs/extensions/reference/manifest/web-accessible-resources).
-
-### Examples
-
-- Onboarding
-- Dashboard
-- FAQ
-- Help
-- Changelog
-
-## Filenames
-
-<EntrypointPatterns
-  :patterns="[
-    ['<name>.html', '<name>.html'],
-    ['<name>/index.html', '<name>.html'],
-  ]"
-/>
-
-Pages are accessible at `'/<name>.html'`:
-
-```ts
-const url = browser.runtime.getURL('/<name>.html');
-
-console.log(url); // "chrome-extension://<id>/<name>.html"
-```
-
-## Definition
-
-```html
-<!doctype html>
-<html lang="en">
-  <head>
-    <meta charset="UTF-8" />
-    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-    <title>Title</title>
-    <!-- Set include/exclude if the page should be removed from some builds -->
-    <meta name="manifest.include" content="['chrome', ...]" />
-    <meta name="manifest.exclude" content="['chrome', ...]" />
-  </head>
-  <body>
-    <!-- ... -->
-  </body>
-</html>
-```

docs/entrypoints/unlisted-scripts.md

@@ -1,37 +0,0 @@
-# Unlisted Scripts
-
-TypeScript files that are bundled and shipped with the extension, but are not included in the manifest.
-
-You are responsible for loading/running these scripts where needed. If necessary, don't forget to add the script and/or any related stylesheets to [`web_accessible_resources`](https://developer.chrome.com/docs/extensions/reference/manifest/web-accessible-resources).
-
-## Filenames
-
-<EntrypointPatterns
-  :patterns="[
-    ['<name>.[jt]sx?', '<name>.js'],
-    ['<name>/index.[jt]sx?', '<name>.js'],
-  ]"
-/>
-
-## Definition
-
-```ts
-export default defineUnlistedScript(() => {
-  // Executed when script is loaded
-});
-```
-
-or
-
-```ts
-export default defineUnlistedScript({
-  // Set include/exclude if the script should be removed from some builds
-  include: undefined | string[],
-  exclude: undefined | string[],
-
-  // Executed when script is loaded
-  main() {
-    // ...
-  },
-});
-```

docs/examples.md

@@ -1,7 +1,19 @@
-# Examples
+---
+layout: page
+---
 
-Simple walkthroughs to accomplish common tasks or patterns with WXT.
+<style>
+.examples-container {
+  padding: 32px;
+}
+</style>
 
-<ExampleList />
+<div class="examples-container">
+  <div class="vp-doc">
+    <h1>Examples</h1>
+  </div>
 
-> Full code available at [`wxt-dev/wxt-examples`](https://github.com/wxt-dev/wxt-examples)
+  <br />
+
+  <ExampleSearch />
+</div>

docs/guide/assets.md

@@ -1,85 +0,0 @@
-# Assets
-
-WXT has two directories for storing assets like CSS, images, or fonts.
-
-- `<srcDir>/public`: Store files that will be copied into the output directory as-is
-- `<srcDir>/assets`: Store files that will be processed by Vite during the build process
-
-## `/public` Directory
-
-Place static files like the extension icon or `_locales/` directory here. These files will be copied over to the output directory without being transformed by Vite.
-
-```
-<srcDir>
-└─ public/
-   ├─ icon-16.png
-   ├─ icon-32.png
-   ├─ icon-48.png
-   ├─ icon-96.png
-   └─ icon-128.png
-```
-
-### Example
-
-You can reference these files by using absolute paths in HTML files or `browser.runtime.getURL` in content scripts.
-
-:::code-group
-
-```html [popup.html]
-<img src="/icon-128.png" />
-```
-
-```ts [content.ts]
-defineContentScript({
-  main() {
-    const image = document.createElement('img');
-    image.src = browser.runtime.getURL('/icon-128.png');
-    document.body.append(image);
-  },
-});
-```
-
-:::
-
-## `/assets` Directory
-
-Files in the assets directory will be processed by Vite. They are imported in your source code, and will be transformed or renamed in the output directory.
-
-```
-<srcDir>
-└─ assets/
-   ├─ style.css
-   └─ illustration.svg
-```
-
-### Example
-
-:::code-group
-
-```html [popup.html]
-<html>
-  <head>
-    <link rel="stylesheet" href="~/assets/style.css" />
-    <!-- ... -->
-  </head>
-  <body>
-    <img src="~/assets/illustration.svg" />
-    <!-- ... -->
-  </body>
-</html>
-```
-
-```ts [content.ts]
-import '~/assets/style.css';
-import illustration from '~/assets/style.svg';
-
-defineContentScript({
-  main() {
-    const image = document.createElement('img');
-    image.src = illustration;
-    document.body.append(image);
-  },
-});
-```
-
-:::

docs/guide/auto-imports.md

@@ -1,80 +0,0 @@
-# Auto-imports
-
-WXT uses the same tool as Nuxt for auto-imports, [`unimport`](https://github.com/unjs/unimport).
-
-:::info Testing
-To setup your test environment for auto-imports, see [Testing](/guide/testing).
-:::
-
-## WXT Auto-imports
-
-Some WXT APIs can be used without importing them:
-
-- [`browser`](/api/wxt/browser/variables/browser) from `wxt/browser`, a small wrapper around `webextension-polyfill`
-- [`defineContentScript`](/api/wxt/sandbox/functions/defineContentScript) from `wxt/sandbox`
-- [`defineBackground`](/api/wxt/sandbox/functions/defineBackground) from `wxt/sandbox`
-- [`defineUnlistedScript`](/api/wxt/sandbox/functions/defineUnlistedScript) from `wxt/sandbox`
-- [`createIntegratedUi`](/api/wxt/client/functions/createIntegratedUi) from `wxt/client`
-- [`createShadowRootUi`](/api/wxt/client/functions/createShadowRootUi) from `wxt/client`
-- [`createIframeUi`](/api/wxt/client/functions/createIframeUi) from `wxt/client`
-- [`fakeBrowser`](/api/wxt/testing/variables/fakeBrowser) from `wxt/testing`
-
-And more!
-
-## Project Auto-imports
-
-In addition WXT APIs, default and named exports from inside the following directories can be used without listing them in imports.
-
-- `<srcDir>/components/*`
-- `<srcDir>/composables/*`
-- `<srcDir>/hooks/*`
-- `<srcDir>/utils/*`
-
-To add auto-imports from subdirectories, like `utils/api/some-file.ts`, re-export them from the base directory:
-
-```ts
-// utils/index.ts
-export * from './api/some-file.ts';
-```
-
-Alternatively, you could add the directory to the list of auto-import directories in your config file.
-
-## TypeScript
-
-For TypeScript to work, you need to run the `wxt prepare` command. This will ensure types are generated for auto-imports.
-
-This should be added to your `postinstall` script:
-
-```json
-// package.json
-{
-  "scripts": {
-    "postinstall": "wxt prepare" // [!code ++]
-  }
-}
-```
-
-## Customization
-
-You can override the default auto-import behavior in your `wxt.config.ts` file.
-
-See [`unimport`'s documentation](https://github.com/unjs/unimport#configurations) for a complete list of options.
-
-```ts
-import { defineConfig } from 'wxt';
-
-export default defineConfig({
-  imports: {
-    // Add auto-imports for vue functions like createApp, ref, computed, watch, toRaw, etc...
-    presets: ['vue'],
-  },
-});
-```
-
-To disable auto-imports, set `imports: false`
-
-```ts
-export default defineConfig({
-  imports: false,
-});
-```

docs/guide/compare.md

@@ -1,50 +0,0 @@
-# Compare
-
-Lets compare the features of WXT vs [Plasmo](https://docs.plasmo.com/framework) (another web extension framework) and [CRXJS](https://crxjs.dev/vite-plugin) (the most popular bundler plugin).
-
-## Overview
-
-| Features                                             |             WXT             |                  Plasmo                  |                                  CRXJS                                  |
-| ---------------------------------------------------- | :-------------------------: | :--------------------------------------: | :---------------------------------------------------------------------: |
-| Supports all browsers                                |             ✅              |                    ✅                    | ❌ See [#56](https://github.com/crxjs/chrome-extension-tools/issues/56) |
-| MV2 Support                                          |             ✅              |                    ✅                    |                          🟡 Either MV2 or MV3                           |
-| MV3 Support                                          |             ✅              |                    ✅                    |                          🟡 Either MV2 or MV3                           |
-| Create Extension ZIPs                                |             ✅              |                    ✅                    |                                   ❌                                    |
-| Create Firefox Sources ZIP                           |             ✅              |                    ❌                    |                                   ❌                                    |
-| First-class TypeScript support                       |             ✅              |                    ✅                    |                                   ✅                                    |
-| Entrypoint discovery                                 |         File based          |                File based                |                                   ❌                                    |
-| Inline entrypoint config                             |             ✅              |                    ✅                    |                             Manifest based                              |
-| Auto-imports                                         |             ✅              |                    ❌                    |                                   ❌                                    |
-| Supports all frontend frameworks                     |             ✅              |      🟡 Only React, Vue, and Svelte      |                                   ✅                                    |
-| Framework specific entrypoints (like `Popup.tsx`)    |   🟡 `.html` `.ts` `.tsx`   | ✅ `.html` `.ts` `.tsx` `.vue` `.svelte` |                                   ❌                                    |
-| Automated publishing                                 |             ✅              |                    ✅                    |                                   ❌                                    |
-| Remote Code Bundling (Google Analytics)              |             ✅              |                    ✅                    |                                   ❌                                    |
-| <strong style="opacity: 50%">Dev Mode</strong>       |                             |                                          |
-| `.env` Files                                         |             ✅              |                    ✅                    |                                   ✅                                    |
-| Opens browser and install extension                  |             ✅              |                    ❌                    |                                   ❌                                    |
-| HMR for UIs                                          |             ✅              |              🟡 React only               |                                   ✅                                    |
-| Reload HTML Files on Change                          |             ✅              |       🟡 Reloads entire extension        |                                   ✅                                    |
-| Reload Content Scripts on Change                     |             ✅              |       🟡 Reloads entire extension        |                                   ✅                                    |
-| Reload Background on Change                          | 🟡 Reloads entire extension |       🟡 Reloads entire extension        |                       🟡 Reloads entire extension                       |
-| Respects Content Script `run_at`                     |             ✅              |                    ✅                    |                 ❌ ESM-style loaders run asynchronously                 |
-| <strong style="opacity: 50%">Built-in Utils</strong> |                             |                                          |                                                                         |
-| Storage                                              |             ✅              |                    ✅                    |                                   ❌                                    |
-| Messaging                                            |             ❌              |                    ✅                    |                                   ❌                                    |
-| Content Script UI                                    |             ✅              |                    ✅                    |                                   ❌                                    |
-
-## Why use WXT?
-
-WXT's main goal is improving the development experience (DX) of creating web extensions, while not sacrificing support. There are two things WXT does differently:
-
-1. Automatically opens a browser with the extension installed when starting development
-2. Reload each part of the extension individually rather than reloading the entire extension
-
-Opening a browser automatically makes it super easy to start and stop development without having to manually load the extension in your browser.
-
-Reloading each part of the extension individually improves your iteration speed while developing UIs. This is because reloading the entire extension on every change will close the popup and any tabs open to an extension page, like options. If you save a file associated with a UI and a content script while working on the UI, it will randomly close because it needed to reload the extension when the content script changed. This interrupts your development flow and is really annoying.
-
-WXT solves this problem by reloading HTML pages and content scripts individually (when possible) to keep your UIs open while you develop them. This is a MV3 feature, so if you're developing a MV2 extension, you'll get the same dev experience as Plasmo.
-
-:::info
-Unfortunately, there isn't an API for reloading the background page/service worker individually, so if you change a file used by the background, the entire extension will reload. See [Issue #53](https://github.com/wxt-dev/wxt/issues/53) for more details.
-:::

docs/guide/configuration.md

@@ -1,99 +0,0 @@
-# Configuration
-
-WXT's behavior can be configured via the `wxt.config.ts` file. In this file, you can add Vite plugins, change the directory structure of your project, and set fields on your `manifest.json`.
-
-## Config File
-
-To configure WXT, create a `wxt.config.ts` file in your project root. It should have the following contents:
-
-```ts
-import { defineConfig } from 'wxt';
-
-export default defineConfig({
-  // My WXT config
-});
-```
-
-:::info
-See the [Config reference](/api/wxt/interfaces/InlineConfig) for a full list of options.
-:::
-
-## Directory Config
-
-WXT allows you to edit several directories to your liking:
-
-- `root` (default: `process.cwd()`) - Root of the WXT project
-- `srcDir` (default: `<rootDir>`) - Location of all your source code
-- `entrypointsDir` (default: `<srcDir>/entrypoints`) - Folder containing all the entrypoints.
-- `publicDir` (default: `<srcDir>/public`) - Folder containing [public assets](/guide/assets)
-
-### Example
-
-You want a `src/` directory to contain all your source code, and you want to rename `entrypoints/` &rarr; `entries/`:
-
-```
-<rootDir>
-├─ src/
-│  └─ entries/
-│     ├─ background.ts
-│     └─ ...
-└─ wxt.config.ts
-```
-
-Your config would look like this:
-
-```ts
-import { defineConfig } from 'wxt';
-
-export default defineConfig({
-  srcDir: 'src',
-  entrypointsDir: 'entries',
-});
-```
-
-## Frontend Frameworks
-
-Adding a framework like Vue, React, or Svelte is easy!
-
-In the `wxt.config.ts` file, install and add the framework's Vite plugin to the config.
-
-:::code-group
-
-```ts [Vue]
-import { defineConfig } from 'wxt';
-import vue from '@vitejs/plugin-vue';
-
-export default defineConfig({
-  vite: () => ({
-    plugins: [vue()],
-  }),
-});
-```
-
-```ts [React]
-import { defineConfig } from 'wxt';
-import react from '@vitejs/plugin-react';
-
-export default defineConfig({
-  vite: () => ({
-    plugins: [react()],
-  }),
-});
-```
-
-```ts [Svelte]
-import { defineConfig } from 'wxt';
-import { svelte } from '@sveltejs/vite-plugin-svelte';
-
-export default defineConfig({
-  vite: () => ({
-    plugins: [svelte()],
-  }),
-});
-```
-
-:::
-
-:::info
-Internally, WXT runs `vite build` multiple times during a single build. It can't share the same instance of some plugins between each build, so a function is used to return completely new instances of each plugin for each build.
-:::

docs/guide/content-script-ui.md

@@ -1,408 +0,0 @@
-# Content Script UI
-
-There are three ways to mount a UI inside a content script:
-
-[[toc]]
-
-Each has their own set of advantages and disadvantages.
-
-| Method      | Isolated Styles |   Isolated Events   | HMR | Use page's context |
-| ----------- | :-------------: | :-----------------: | :-: | :----------------: |
-| Integrated  |       ❌        |         ❌          | ❌  |         ✅         |
-| Shadow Root |       ✅        | ✅ (off by default) | ❌  |         ✅         |
-| IFrame      |       ✅        |         ✅          | ✅  |         ❌         |
-
-## Integrated
-
-Integrated content script UIs are injected alongside the content of a page. This means that they are affected by CSS on that page.
-
-:::code-group
-
-```ts [Vanilla]
-// entrypoints/example-ui.content.ts
-export default defineContentScript({
-  matches: ['<all_urls>'],
-
-  main(ctx) {
-    const ui = createIntegratedUi(ctx, {
-      position: 'inline',
-      onMount: (container) => {
-        // Append children to the container
-        const app = document.createElement('p');
-        app.textContent = '...';
-        container.append(app);
-      },
-    });
-
-    // Call mount to add the UI to the DOM
-    ui.mount();
-  },
-});
-```
-
-```ts [Vue]
-// entrypoints/example-ui.content/index.ts
-import { createApp } from 'vue';
-import App from './App.vue';
-
-export default defineContentScript({
-  matches: ['<all_urls>'],
-
-  main(ctx) {
-    const ui = createIntegratedUi(ctx, {
-      position: 'inline',
-      onMount: (container) => {
-        // Create the app and mount it to the UI container
-        const app = createApp(App);
-        app.mount(container);
-        return app;
-      },
-      onRemove: (app) => {
-        // Unmount the app when the UI is removed
-        app.unmount();
-      },
-    });
-
-    // Call mount to add the UI to the DOM
-    ui.mount();
-  },
-});
-```
-
-```tsx [React]
-// entrypoints/example-ui.content/index.tsx
-import ReactDOM from 'react-dom/client';
-import App from './App.tsx';
-
-export default defineContentScript({
-  matches: ['<all_urls>'],
-
-  main(ctx) {
-    const ui = createIntegratedUi(ctx, {
-      position: 'inline',
-      onMount: (container) => {
-        // Create a root on the UI container and render a component
-        const root = ReactDOM.createRoot(container);
-        root.render(<App />);
-        return root;
-      },
-      onRemove: (root) => {
-        // Unmount the root when the UI is removed
-        root.unmount();
-      },
-    });
-
-    // Call mount to add the UI to the DOM
-    ui.mount();
-  },
-});
-```
-
-```ts [Svelte]
-// entrypoints/example-ui.content/index.ts
-import App from './App.svelte';
-
-export default defineContentScript({
-  matches: ['<all_urls>'],
-
-  main(ctx) {
-    const ui = createIntegratedUi(ctx, {
-      position: 'inline',
-      onMount: (container) => {
-        // Create the Svelte app inside the UI container
-        const app = new App({
-          target: container,
-        });
-        return app;
-      },
-      onRemove: (app) => {
-        // Destroy the app when the UI is removed
-        app.$destroy();
-      },
-    });
-
-    // Call mount to add the UI to the DOM
-    ui.mount();
-  },
-});
-```
-
-```tsx [Solid]
-// entrypoints/example-ui.content/index.ts
-import { render } from 'solid-js/web';
-
-export default defineContentScript({
-  matches: ['<all_urls>'],
-
-  main(ctx) {
-    const ui = createIntegratedUi(ctx, {
-      position: 'inline',
-      onMount: (container) => {
-        // Render your app to the UI container
-        const unmount = render(() => <div>...</div>, container);
-      },
-      onRemove: (unmount) => {
-        // Unmount the app when the UI is removed
-        unmount();
-      },
-    });
-
-    // Call mount to add the UI to the DOM
-    ui.mount();
-  },
-});
-```
-
-:::
-
-See the [API Reference](/api/wxt/client/functions/createIntegratedUi) for the complete list of options.
-
-You can control how CSS is injected for an integrated content script UI with the [`cssInjectionMode`](/api/wxt/interfaces/BaseContentScriptEntrypointOptions#cssinjectionmode) property. Usually, you'll want to leave it as `"manifest"`, the default, so the UI inherits its style from the website's CSS.
-
-## Shadow Root
-
-Often in web extensions, you don't want your content script's CSS affecting the page, or vise-versa. The [`ShadowRoot`](https://developer.mozilla.org/en-US/docs/Web/API/ShadowRoot) API is ideal for this.
-
-WXT's [`createShadowRootUi`](/api/wxt/client/functions/createShadowRootUi) abstracts all the `ShadowRoot` setup away, making it easy to create UIs with isolated CSS. It also supports an optional `isolateEvents` parameter to further isolate user interactions.
-
-To use `createShadowRootUi`, follow these steps:
-
-1. Import your CSS file at the top of your content script
-2. Set [`cssInjectionMode: "ui"`](/api/wxt/interfaces/BaseContentScriptEntrypointOptions#cssinjectionmode) inside `defineContentScript`
-3. Define your UI with `createShadowRootUi()`
-4. Mount the UI so it is visible to users
-
-:::code-group
-
-```ts [Vanilla]
-// 1. Import the style
-import './style.css';
-
-export default defineContentScript({
-  matches: ['<all_urls>'],
-  // 2. Set cssInjectionMode
-  cssInjectionMode: 'ui',
-
-  async main(ctx) {
-    // 3. Define your UI
-    const ui = await createShadowRootUi(ctx, {
-      name: 'example-ui',
-      position: 'inline',
-      onMount(container) {
-        // Define how your UI will be mounted inside the container
-        const app = document.createElement('p');
-        app.textContent = 'Hello world!';
-        container.append(app);
-      },
-    });
-
-    // 4. Mount the UI
-    ui.mount();
-  },
-});
-```
-
-```ts [Vue]
-// 1. Import the style
-import './style.css';
-import { createApp } from 'vue';
-import App from './App.vue';
-
-export default defineContentScript({
-  matches: ['<all_urls>'],
-  // 2. Set cssInjectionMode
-  cssInjectionMode: 'ui',
-
-  async main(ctx) {
-    // 3. Define your UI
-    const ui = await createShadowRootUi(ctx, {
-      name: 'example-ui',
-      position: 'inline',
-      onMount: (container) => {
-        // Define how your UI will be mounted inside the container
-        const app = createApp(App);
-        app.mount(container);
-        return app;
-      },
-      onRemove: (app) => {
-        // Unmount the app when the UI is removed
-        app?.unmount();
-      },
-    });
-
-    // 4. Mount the UI
-    ui.mount();
-  },
-});
-```
-
-```tsx [React]
-// 1. Import the style
-import './style.css';
-import ReactDOM from 'react-dom/client';
-import App from './App.tsx';
-
-export default defineContentScript({
-  matches: ['<all_urls>'],
-  // 2. Set cssInjectionMode
-  cssInjectionMode: 'ui',
-
-  async main(ctx) {
-    // 3. Define your UI
-    const ui = await createShadowRootUi(ctx, {
-      name: 'example-ui',
-      position: 'inline',
-      onMount: (container) => {
-        // Container is a body, and React warns when creating a root on the body, so create a wrapper div
-        const app = document.createElement('div');
-        container.append(app);
-
-        // Create a root on the UI container and render a component
-        const root = ReactDOM.createRoot(app);
-        root.render(<App />);
-        return root;
-      },
-      onRemove: (root) => {
-        // Unmount the root when the UI is removed
-        root?.unmount();
-      },
-    });
-
-    // 4. Mount the UI
-    ui.mount();
-  },
-});
-```
-
-```ts [Svelte]
-// 1. Import the style
-import './style.css';
-import App from './App.svelte';
-
-export default defineContentScript({
-  matches: ['<all_urls>'],
-  // 2. Set cssInjectionMode
-  cssInjectionMode: 'ui',
-
-  async main(ctx) {
-    // 3. Define your UI
-    const ui = await createShadowRootUi(ctx, {
-      name: 'example-ui',
-      position: 'inline',
-      onMount: (container) => {
-        // Create the Svelte app inside the UI container
-        const app = new App({
-          target: container,
-        });
-        return app;
-      },
-      onRemove: (app) => {
-        // Destroy the app when the UI is removed
-        app?.$destroy();
-      },
-    });
-
-    // 4. Mount the UI
-    ui.mount();
-  },
-});
-```
-
-```tsx [Solid]
-// 1. Import the style
-import './style.css';
-import { render } from 'solid-js/web';
-
-export default defineContentScript({
-  matches: ['<all_urls>'],
-  // 2. Set cssInjectionMode
-  cssInjectionMode: 'ui',
-
-  async main(ctx) {
-    // 3. Define your UI
-    const ui = await createShadowRootUi(ctx, {
-      name: 'example-ui',
-      position: 'inline',
-      onMount: (container) => {
-        // Render your app to the UI container
-        const unmount = render(() => <div>...</div>, container);
-      },
-      onRemove: (unmount) => {
-        // Unmount the app when the UI is removed
-        unmount?.();
-      },
-    });
-
-    // 4. Mount the UI
-    ui.mount();
-  },
-});
-```
-
-:::
-
-See the [API Reference](/api/wxt/client/functions/createShadowRootUi) for the complete list of options.
-
-:::info TailwindCSS
-`createShadowRootUi` supports TailwindCSS out of the box! When importing the styles, just import the main CSS file containing the `@tailwind` directives, and everything will just work :+1:.
-:::
-
-## IFrame
-
-If you don't need to run your UI in the same frame as the content script, you can use an IFrame to host your UI instead. Since an IFrame just hosts an HTML page, **_HMR is supported_**.
-
-WXT provides a helper function, [`createIframeUi`](/api/wxt/client/functions/createIframeUi), which simplifies setting up the IFrame.
-
-1. Create an HTML page that will be loaded into your IFrame
-   ```html
-   <!-- entrypoints/example-iframe.html -->
-   <!doctype html>
-   <html lang="en">
-     <head>
-       <meta charset="UTF-8" />
-       <meta name="viewport" content="width=device-width, initial-scale=1.0" />
-       <title>Your Content Script IFrame</title>
-     </head>
-     <body>
-       <!-- ... -->
-     </body>
-   </html>
-   ```
-1. Add the page to the manifest's `web_accessible_resources`
-   ```ts
-   // wxt.config.ts
-   export default defineConfig({
-     manifest: {
-       web_accessible_resources: [
-         {
-           resources: ['example-iframe.html'],
-           matches: [...],
-         },
-       ],
-     },
-   });
-   ```
-1. Create and mount the IFrame
-
-   ```ts
-   export default defineContentScript({
-     matches: ['<all_urls>'],
-
-     main(ctx) {
-       // Define the UI
-       const ui = createIframeUi(ctx, {
-         page: '/example-iframe.html',
-         position: 'inline',
-         onMount: (wrapper, iframe) => {
-           // Add styles to the iframe like width
-           iframe.width = '123';
-         },
-       });
-
-       // Show UI to user
-       ui.mount();
-     },
-   });
-   ```
-
-See the [API Reference](/api/wxt/client/functions/createIframeUi) for the complete list of options.

docs/guide/development.md

@@ -1,116 +0,0 @@
-# Development
-
-WXT's main goal is providing the best DX it possibly can. When running your extension in dev mode, each part of your extension is reloaded separately when possible.
-
-|                     | HMR | Reloaded individually | Reload extension |                    Restart browser                     |
-| ------------------- | :-: | :-------------------: | :--------------: | :----------------------------------------------------: |
-| HTML File           |     |          ✅           |
-| HTML Dependency     | ✅  |
-| MV3 Content Script  |     |          ✅           |
-| MV2 Content Script  |     |                       |        ✅        |
-| Background          |     |                       |        ✅        |
-| manifest.json       |     |                       |                  | 🟡 See [#16](https://github.com/wxt-dev/wxt/issues/16) |
-| `wxt.config.ts`     |     |                       |                  | 🟡 See [#10](https://github.com/wxt-dev/wxt/issues/10) |
-| `web-ext.config.ts` |     |                       |                  | 🟡 See [#10](https://github.com/wxt-dev/wxt/issues/10) |
-
-## Dev Mode vs Production Builds
-
-There are some notable differences between the development and production versions of an extension. During development:
-
-1. **Content scripts are not listed in the `manifest.json`** when targeting MV3. Instead, the [`scripting`](https://developer.chrome.com/docs/extensions/reference/api/scripting) permission is used to register content scripts at runtime so they can be reloaded individually.
-
-   To get the list of content scripts during development, run the following in the background's console:
-
-   ```ts
-   await chrome.scripting.getRegisteredContentScripts();
-   ```
-
-2. **The CSP is modified to allow loading scripts from the dev server**. Make sure you're using Chrome v110 or above for HMR to work.
-
-3. If you don't include a background script/service worker, one will be created to perform various tasks in dev mode, mostly related to reloading different parts of the extension on change.
-
-For production builds, none of the above modifications will be applied, and you're extension/manifest will only include what you have defined.
-
-## Configure Browser Startup
-
-WXT uses [`web-ext` by Mozilla](https://github.com/mozilla/web-ext) to automatically open a browser with the extension installed. You can configure the runner's behavior via the [`runner`](/api/wxt/interfaces/InlineConfig#runner) option, or in a separate gitignored file, `web-ext.config.ts`.
-
-:::code-group
-
-```ts [wxt.config.ts]
-import { defineConfig } from 'wxt';
-
-export default defineConfig({
-  runner: {
-    // Runner config
-  },
-});
-```
-
-```ts [web-ext.config.ts]
-import { defineRunnerConfig } from 'wxt';
-
-export default defineRunnerConfig({
-  // Runner config
-});
-```
-
-:::
-
-### Browser Binaries
-
-`web-ext`'s browser discovery is very limited. By default, it only guesses at where Chrome and Firefox are installed. If you've customized your install locations, you may need to tell `web-ext` where the binaries/executables are located using the [`binaries` option](/api/wxt/interfaces/ExtensionRunnerConfig#binaries). For other Chromium based browsers, like Edge or Opera, you'll need to explicitly list them in the `binaries` option as well, otherwise they will open in Chrome by default.
-
-```ts
-// ~/web-ext.config.ts
-import { defineRunnerConfig } from 'wxt';
-
-export default defineRunnerConfig({
-  binaries: {
-    chrome: '/path/to/chrome-beta', // Use Chrome Beta instead of regular Chrome
-    firefox: 'firefoxdeveloperedition', // Use Firefox Developer Edition instead of regular Firefox
-    edge: '/path/to/edge', // Open MS Edge when running "wxt -b edge"
-  },
-});
-```
-
-:::tip
-When configuring browser binaries, it's helpful to put them in `~/web-ext.config.ts` instead of the project directory's `web-ext.config.ts` file. When placed in your home directory (`~/`), this config will be used by all WXT projects, so you only need to configure the binaries once.
-:::
-
-### Other options
-
-You can customize other options as well, like startup URLs, profiles, or additional command line arguments:
-
-```ts
-// web-ext.config.ts
-import { defineRunnerConfig } from 'wxt';
-
-export default defineRunnerConfig({
-  startUrls: ['https://google.com', 'https://duckduckgo.com'],
-  chromiumProfile: '/path/to/profile/to/use',
-  chromiumArgs: ['--window-size=400,300'],
-});
-```
-
-For a full list of options, see the [API Reference](/api/wxt/interfaces/ExtensionRunnerConfig).
-
-## Reload the Extension
-
-Normally, to manually reload an extension, you have to visit `chrome://extensions` and click the reload button for your extension.
-
-When running `wxt` command to start the dev server, WXT adds a keyboard shortcut `Alt+R`, that reloads the extension when pressed, without visiting `chrome://extensions`. This can also be customized or disabled:
-
-```ts [wxt.config.ts]
-import { defineConfig } from 'wxt';
-
-export default defineConfig({
-  dev: {
-    reloadCommand: 'Alt+T', // false, to disable
-  },
-});
-```
-
-:::info
-This shortcut is only available during development, and is not be added to your extension when running `wxt build` or `wxt-zip`.
-:::

docs/guide/entrypoints.md

@@ -1,141 +0,0 @@
-# Defining Entrypoints
-
-An "entrypoint" is any HTML, JS, or CSS file that needs to be bundled and included with the extension.
-
-Entrypoints may or may not be listed in the extension's `manifest.json`.
-
-## `/entrypoints` Directory
-
-In WXT, entrypoints are defined by adding a file to the `entrypoints/` directory.
-
-For example, a project that looks like this:
-
-```
-<rootDir>
-└─ entrypoints/
-   ├─ background.ts
-   ├─ content.ts
-   ├─ injected.ts
-   └─ popup.html
-```
-
-would result in the following `manifest.json`:
-
-```json
-{
-  // ...
-  "manifest_version": 3,
-  "action": {
-    // ...
-    "default_popup": "popup.html"
-  },
-  "background": {
-    // ...
-    "service_worker": "background.js"
-  },
-  "content_scripts": [
-    {
-      // ...
-      "js": ["content-scripts/content.js"]
-    }
-  ]
-}
-```
-
-If a file uses a special name recognized by WXT, it will be added to the manifest. In this case:
-
-- `popup.html` &rarr; `action.default_popup`
-- `content.ts` &rarr; `content_scripts.0.js.0`
-- `background.ts` &rarr; `background.service_worker`
-
-But not all entrypoints are added to the `manifest.json`. If the filename is not recognized by WXT, they are still built and included in the extension, but they are considered "unlisted" and are not apart of the manifest.
-
-In this case, `injected.ts` gets output to `<outdir>/injected.js` and is accessible via `browser.runtime.getURL("/injected.js")`.
-
-:::info
-See [`/entrypoints` folder](/entrypoints/background) documentation for a full list of recognized entrypoint filenames.
-:::
-
-## Entrypoint Options
-
-Some entrypoints, like content scripts, actions, or the background, can receive additional options.
-
-In HTML files, options are listed as `meta` tags:
-
-```html
-<html>
-  <head>
-    <!-- Defining the popup's "default_icon" field -->
-    <meta name="manifest.default_icon" content="{ '16': '/icon/16.png' }" />
-  </head>
-</html>
-```
-
-In TS files, options are apart of the file's default export:
-
-```ts
-export default defineContentScript({
-  matches: ['*://*.google.com/*'],
-  runAt: 'document_start',
-  main() {
-    // ...
-  },
-});
-```
-
-:::info
-For a full list of entrypoints and each of their options, see the [`/entrypoints` folder](/entrypoints/background) documentation.
-:::
-
-### Side Effects
-
-You cannot use imported variables outside the `main` function in JS entrypoints. This includes options, as shown below:
-
-```ts
-// entrypoints/content.ts
-import { GOOGLE_MATCHES } from '~/utils/match-patterns';
-
-export default defineContentScript({
-  matches: GOOGLE_MATCHES,
-  main() {
-    // ...
-  },
-});
-```
-
-```
-$ wxt build
-wxt build
-
-WXT 0.14.1
-ℹ Building chrome-mv3 for production with Vite 5.0.5
-✖ Command failed after 360 ms
-
-[8:55:54 AM]  ERROR  entrypoints/content.ts: Cannot use imported variable "GOOGLE_MATCHES" before main function. See https://wxt.dev/guide/entrypoints.html#side-effects
-```
-
-This throws an error because WXT needs to import each entrypoint during the build process to extract its definition (containing the `match`, `runAt`, `include`/`exclude`, etc.) to render the `manifest.json` correctly. Before loading an entrypoint, a transformation is applied to remove all imports. This prevents imported modules (local or NPM) with side-effects from running during the build process, potentially throwing an error.
-
-:::details Why?
-
-When importing your entrypoint to get its definition, the file is imported in a **_node environment_**, and doesn't have access to the `window`, `chrome`, or `browser` globals a web extension usually has access to. If WXT doesn't remove all the imports from the file, the imported modules could try and access one of these variables, throwing an error.
-
-:::
-
-:::warning
-See [`wxt-dev/wxt#336`](https://github.com/wxt-dev/wxt/issues/336) to track the status of this bug.
-:::
-
-Usually, this error occurs when you try to extract options into a shared file or try to run code outside the `main` function. To fix the example from above, use literal values when defining an entrypoint instead of importing them:
-
-```ts
-import { GOOGLE_MATCHES } from '~/utils/match-patterns'; // [!code --]
-
-export default defineContentScript({
-  matches: GOOGLE_MATCHES, // [!code --]
-  matches: ['*//*.google.com/*'], // [!code ++]
-  main() {
-    // ...
-  },
-});
-```

docs/guide/esm.md

@@ -1,38 +0,0 @@
-# ES Modules
-
-Configure entrypoints to use ESM at runtime.
-
-Currently, ESM entrypoints are opt-in, so you must configure each entrypoint with that in mind.
-
-## HTML Pages <Badge type="warning" text="≥0.0.1" />
-
-In general, you should always make HTML pages import ESM scripts, unless you need to support old browsers.
-
-To make a script ESM, add `type="module"`:
-
-<!-- prettier-ignore -->
-```html
-<script src="./main.ts"></script> <!-- [!code --] -->
-<script src="./main.ts" type="module"></script> <!-- [!code ++] -->
-```
-
-## Background <Badge type="warning" text="≥0.16.0" />
-
-In your background script, set `type: "module"`:
-
-```ts
-export default defineBackground({
-  type: 'module', // !code ++
-  main() {
-    // ...
-  },
-});
-```
-
-:::warning
-Only MV3 support ESM background scripts/service workers. When targeting MV2, the `type` option is ignored and the background is always bundled into a single file as IIFE.
-:::
-
-## Content Scripts
-
-Coming soon. Follow [Content Script ESM Support #357](https://github.com/wxt-dev/wxt/issues/357) for updates.

docs/guide/essentials/assets.md

@@ -0,0 +1,188 @@
+# Assets
+
+## `/assets` Directory
+
+Any assets imported or referenced inside the `<srcDir>/assets/` directory will be processed by WXT's bundler.
+
+Here's how you access them:
+
+:::code-group
+
+```ts [JS]
+import imageUrl from '~/assets/image.png';
+
+const img = document.createElement('img');
+img.src = imageUrl;
+```
+
+```html [HTML]
+<!-- In HTML tags, you must use the relative path --->
+<img src="../assets/image.png" />
+```
+
+```css [CSS]
+.bg-image {
+  background-image: url(~/assets/image.png);
+}
+```
+
+```vue [Vue]
+<script>
+import image from '~/assets/image.png';
+</script>
+
+<template>
+  <img :src="image" />
+</template>
+```
+
+```jsx [JSX]
+import image from '~/assets/image.png';
+
+<img src={image} />;
+```
+
+:::
+
+## `/public` Directory
+
+Files inside `<rootDir>/public/` are copied into the output folder as-is, without being processed by WXT's bundler.
+
+Here's how you access them:
+
+:::code-group
+
+```ts [JS]
+import imageUrl from '/image.png';
+
+const img = document.createElement('img');
+img.src = imageUrl;
+```
+
+```html [HTML]
+<img src="/image.png" />
+```
+
+```css [CSS]
+.bg-image {
+  background-image: url(/image.png);
+}
+```
+
+```vue [Vue]
+<template>
+  <img src="/image.png" />
+</template>
+```
+
+```jsx [JSX]
+<img src="/image.png" />
+```
+
+:::
+
+:::warning
+Assets in the `public/` directory are **_not_** accessible in content scripts by default. To use a public asset in a content script, you must add it to your manifest's [`web_accessible_resources` array](/api/reference/wxt/type-aliases/UserManifest#web-accessible-resources).
+:::
+
+## Inside Content Scripts
+
+Assets inside content scripts are a little different. By default, when you import an asset, it returns just the path to the asset. This is because Vite assumes you're loading assets from the same hostname.
+
+But, inside content scripts, the hostname is whatever the tab is set to. So if you try to fetch the asset, manually or as an `<img>`'s `src`, it will be loaded from the tab's website, not your extension.
+
+To fix this, you need to convert the image to a full URL using `browser.runtime.getURL`:
+
+```ts [entrypoints/content.ts]
+import iconUrl from '/icon/128.png';
+
+export default defineContentScript({
+  matches: ['*://*.google.com/*'],
+  main() {
+    console.log(iconUrl); // "/icon/128.png"
+    console.log(browser.runtime.getURL(iconUrl)); // "chrome-extension://<id>/icon/128.png"
+  },
+});
+```
+
+## WASM
+
+How a `.wasm` file is loaded varies greatly between packages, but most follow a basic setup: Use a JS API to load and execute the `.wasm` file.
+
+For an extension, that means two things:
+
+1. The `.wasm` file needs to be present in output folder so it can be loaded.
+2. You must import the JS API to load and initialize the `.wasm` file, usually provided by the NPM package.
+
+For an example, let's say you have a content script needs to parse TS code into AST. We'll use [`@oxc-parser/wasm`](https://www.npmjs.com/package/@oxc-parser/wasm) to do it!
+
+First, we need to copy the `.wasm` file to the output directory. We'll do it with a [WXT module](/guide/essentials/wxt-modules):
+
+```ts
+// modules/oxc-parser-wasm.ts
+import { resolve } from 'node:path';
+
+export default defineWxtModule((wxt) => {
+  wxt.hook('build:publicAssets', (_, assets) => {
+    assets.push({
+      absoluteSrc: resolve(
+        'node_modules/@oxc-parser/wasm/web/oxc_parser_wasm_bg.wasm',
+      ),
+      relativeDest: 'oxc_parser_wasm_bg.wasm',
+    });
+  });
+});
+```
+
+Run `wxt build`, and you should see the WASM file copied into your `.output/chrome-mv3` folder!
+
+Next, since this is in a content script and we'll be fetching the WASM file over the network to load it, we need to add the file to the `web_accessible_resources`:
+
+```ts [wxt.config.ts]
+export default defineConfig({
+  manifest: {
+    web_accessible_resources: [
+      {
+        // We'll use this matches in the content script as well
+        matches: ['*://*.github.com/*'],
+        // Use the same path as `relativeDest` from the WXT module
+        resources: ['/oxc_parser_wasm_bg.wasm'],
+      },
+    ],
+  },
+});
+```
+
+And finally, we need to load and initialize the `.wasm` file inside the content script to use it:
+
+```ts [entrypoints/content.ts]
+import initWasm, { parseSync } from '@oxc-parser/wasm';
+
+export default defineContentScript({
+  matches: '*://*.github.com/*',
+  async main(ctx) {
+    if (!location.pathname.endsWith('.ts')) return;
+
+    // Get text from GitHub
+    const code = document.getElementById(
+      'read-only-cursor-text-area',
+    )?.textContent;
+    if (!code) return;
+    const sourceFilename = document.getElementById('file-name-id')?.textContent;
+    if (!sourceFilename) return;
+
+    // Load the WASM file:
+    await initWasm({
+      module_or_path: browser.runtime.getURL('/oxc_parser_wasm_bg.wasm'),
+    });
+
+    // Once loaded, we can use `parseSync`!
+    const ast = parseSync(code, { sourceFilename });
+    console.log(ast);
+  },
+});
+```
+
+This code is taken directly from `@oxc-parser/wasm` docs with one exception: We manually pass in a file path. In a standard NodeJS or web project, the default path works just fine so you don't have to pass anything in. However, extensions are different. You should always explicitly pass in the full URL to the WASM file in your output directory, which is what `browser.runtime.getURL` returns.
+
+Run your extension, and you should see OXC parse the TS file!

docs/guide/essentials/config/auto-imports.md

@@ -0,0 +1,118 @@
+# Auto-imports
+
+WXT uses [`unimport`](https://www.npmjs.com/package/unimport), the same tool as Nuxt, to setup auto-imports.
+
+```ts
+export default defineConfig({
+  // See https://www.npmjs.com/package/unimport#configurations
+  imports: {
+    // ...
+  },
+});
+```
+
+By default, WXT automatically sets up auto-imports for all of it's own APIs and some of your project directories:
+
+- `<srcDir>/components/*`
+- `<srcDir>/composables/*`
+- `<srcDir>/hooks/*`
+- `<srcDir>/utils/*`
+
+All named and default exports from files in these directories are available everywhere else in your project without having to import them.
+
+To see the complete list of auto-imported APIs, run [`wxt prepare`](/api/cli/wxt-prepare) and look at your project's `.wxt/types/imports-module.d.ts` file.
+
+## TypeScript
+
+For TypeScript and your editor to recognize auto-imported variables, you need to run the [`wxt prepare` command](/api/cli/wxt-prepare).
+
+Add this command to your `postinstall` script so your editor has everything it needs to report type errors after installing dependencies:
+
+```jsonc
+// package.json
+{
+  "scripts": {
+    "postinstall": "wxt prepare", // [!code ++]
+  },
+}
+```
+
+## ESLint
+
+ESLint doesn't know about the auto-imported variables unless they are explicitly defined in the ESLint's `globals`. By default, WXT will generate the config if it detects ESLint is installed in your project. If the config isn't generated automatically, you can manually tell WXT to generate it.
+
+:::code-group
+
+```ts [ESLint >=9]
+export default defineConfig({
+  imports: {
+    eslintrc: {
+      enabled: 9,
+    },
+  },
+});
+```
+
+```ts [ESLint <=8]
+export default defineConfig({
+  imports: {
+    eslintrc: {
+      enabled: 8,
+    },
+  },
+});
+```
+
+:::
+
+Then in your ESLint config, import and use the generated file:
+
+:::code-group
+
+```js [ESLint >=9]
+// eslint.config.mjs
+import autoImports from './.wxt/eslint-auto-imports.mjs';
+
+export default [
+  autoImports,
+  {
+    // The rest of your config...
+  },
+];
+```
+
+```js [ESLint <=8]
+// .eslintrc.mjs
+export default {
+  extends: ['./.wxt/eslintrc-auto-import.json'],
+  // The rest of your config...
+};
+```
+
+:::
+
+## Disabling Auto-imports
+
+Not all developers like auto-imports. To disable them, set `imports` to `false`.
+
+```ts
+export default defineConfig({
+  imports: false, // [!code ++]
+});
+```
+
+## Explicit Imports (`#imports`)
+
+You can manually import all of WXT's APIs via the `#imports` module:
+
+```ts
+import {
+  createShadowRootUi,
+  ContentScriptContext,
+  MatchPattern,
+} from '#imports';
+```
+
+To learn more about how the `#imports` module works, read the [related blog post](/blog/2024-12-06-using-imports-module).
+
+If you've disabled auto-imports, you should still use `#imports` to import all of WXT's APIs from a single place.

docs/guide/essentials/config/browser-startup.md

@@ -0,0 +1,134 @@
+---
+outline: deep
+---
+
+# Browser Startup
+
+During development, WXT will use any of the below packages to automatically open a browser with your extension installed.
+
+- [`web-ext` by Mozilla](https://www.npmjs.com/package/web-ext)
+
+Just install the dependency you want WXT to use to open the browser.
+
+## `web-ext` Usage
+
+> See the [API Reference](/api/reference/wxt/interfaces/WebExtConfig) for a full list of config.
+
+### Config Files
+
+You can configure browser startup in 3 places:
+
+1. `<rootDir>/web-ext.config.ts`: Ignored from version control, this file lets you configure your own options for a specific project without affecting other developers
+
+   ```ts [web-ext.config.ts]
+   import { defineWebExtConfig } from 'wxt';
+
+   export default defineWebExtConfig({
+     // ...
+   });
+   ```
+
+2. `<rootDir>/wxt.config.ts`: Via the [`webExt` config](/api/reference/wxt/interfaces/InlineConfig#webext), included in version control
+3. `$HOME/web-ext.config.ts`: Provide default values for all WXT projects on your computer
+
+### Recipes
+
+#### Set Browser Binaries
+
+To set or customize the browser opened during development:
+
+```ts [web-ext.config.ts]
+import { defineWebExtConfig } from 'wxt';
+
+export default defineWebExtConfig({
+  binaries: {
+    chrome: '/path/to/chrome-beta', // Use Chrome Beta instead of regular Chrome
+    firefox: 'firefoxdeveloperedition', // Use Firefox Developer Edition instead of regular Firefox
+    edge: '/path/to/edge', // Open MS Edge when running "wxt -b edge"
+  },
+});
+```
+
+```ts [wxt.config.ts]
+export default defineConfig({
+  webExt: {
+    binaries: {
+      chrome: '/path/to/chrome-beta', // Use Chrome Beta instead of regular Chrome
+      firefox: 'firefoxdeveloperedition', // Use Firefox Developer Edition instead of regular Firefox
+      edge: '/path/to/edge', // Open MS Edge when running "wxt -b edge"
+    },
+  },
+});
+```
+
+By default, WXT will try to automatically discover where Chrome/Firefox are installed. However, if you have chrome installed in a non-standard location, you need to set it manually as shown above.
+
+#### Persist Data
+
+By default, to keep from modifying your browser's existing profiles, `web-ext` creates a brand new profile every time you run the `dev` script.
+
+Right now, Chromium based browsers are the only browsers that support overriding this behavior and persisting data when running the `dev` script multiple times.
+
+To persist data, set the `--user-data-dir` flag in any of the config files mentioned above:
+
+:::code-group
+
+```ts [Mac/Linux]
+import { defineWebExtConfig } from 'wxt';
+
+export default defineWebExtConfig({
+  chromiumArgs: ['--user-data-dir=./.wxt/chrome-data'],
+});
+```
+
+```ts [Windows]
+import { resolve } from 'node:path';
+import { defineWebExtConfig } from 'wxt';
+
+export default defineWebExtConfig({
+  // On Windows, the path must be absolute
+  chromiumProfile: resolve('.wxt/chrome-data'),
+  keepProfileChanges: true,
+});
+```
+
+:::
+
+Now, next time you run the `dev` script, a persistent profile will be created in `.wxt/chrome-data/{profile-name}`. With a persistent profile, you can install devtools extensions to help with development, allow the browser to remember logins, etc, without worrying about the profile being reset the next time you run the `dev` script.
+
+:::tip
+You can use any directory you'd like for `--user-data-dir`, the examples above create a persistent profile for each WXT project. To create a profile for all WXT projects, you can put the `chrome-data` directory inside your user's home directory.
+:::
+
+#### Disable Opening Browser
+
+If you don't want to uninstall `web-ext`, like to test in your normal profile, you can do so via `disabled: true`:
+
+```ts [web-ext.config.ts]
+import { defineWebExtConfig } from 'wxt';
+
+export default defineWebExtConfig({
+  disabled: true,
+});
+```
+
+### Enabling Chrome Features
+
+Some APIs are disabled in Chrome during development because of the default flags `web-ext` uses to launch Chrome, like the [Prompt API](https://developer.chrome.com/docs/ai/prompt-api).
+
+If your extension depends on new features or services, you can enable them via `chromiumArgs`:
+
+```ts
+import { defineWebExtConfig } from 'wxt';
+
+export default defineWebExtConfig({
+  chromiumArgs: [
+    // For example, this flag enables the Prompt API
+    '--disable-features=DisableLoadExtensionCommandLineSwitch',
+  ],
+});
+```
+
+There is no comprehensive list of what feature flags enable what APIs and services.
+
+Alternatively, if you can't find a flag that enables a feature you're looking for, [disable the opening the browser during development](#disable-opening-browser) and use your regular chrome profile for development.

docs/guide/essentials/config/build-mode.md

@@ -0,0 +1,29 @@
+# Build Modes
+
+Because WXT is powered by Vite, it supports [modes](https://vite.dev/guide/env-and-mode.html#modes) in the same way.
+
+When running any dev or build commands, pass the `--mode` flag:
+
+```sh
+wxt --mode production
+wxt build --mode development
+wxt zip --mode testing
+```
+
+By default, `--mode` is `development` for the dev command and `production` for all other commands (build, zip, etc).
+
+## Get Mode at Runtime
+
+You can access the current mode in your extension using `import.meta.env.MODE`:
+
+```ts
+switch (import.meta.env.MODE) {
+  case 'development': // ...
+  case 'production': // ...
+
+  // Custom modes specified with --mode
+  case 'testing': // ...
+  case 'staging': // ...
+  // ...
+}
+```

docs/guide/essentials/config/entrypoint-loaders.md

@@ -0,0 +1,19 @@
+# Entrypoint Loaders
+
+To generate the manifest and other files at build-time, WXT must import each entrypoint to get their options, like content script `matches`. For HTML files, this is easy. For JS/TS entrypoints, the process is more complicated.
+
+When loading your JS/TS entrypoints, they are imported into a NodeJS environment, not the `browser` environment that they normally run in. This can lead to issues commonly seen when running browser-only code in a NodeJS environment, like missing global variables.
+
+WXT does several pre-processing steps to try and prevent errors during this process:
+
+1. Use `linkedom` to make a small set of browser globals (`window`, `document`, etc) available.
+2. Use `@webext-core/fake-browser` to create a fake version of the `chrome` and `browser` globals expected by extensions.
+3. Pre-process the JS/TS code, stripping out the `main` function then tree-shaking unused code from the file
+
+However, this process is not perfect. It doesn't setup all the globals found in the browser and the APIs may behave differently. As such, **_you should avoid using browser or extension APIs outside the `main` function of your entrypoints!_** See [Entrypoint Limitations](/guide/essentials/extension-apis#entrypoint-limitations) for more details.
+
+:::tip
+If you're running into errors while importing entrypoints, run `wxt prepare --debug` to see more details about this process. When debugging, WXT will print out the pre-processed code to help you identify issues.
+:::
+
+Once the environment has been polyfilled and your code pre-processed, it's up the entrypoint loader to import your code, extracting the options from the default export.