No service worker shown in Chrome extensions after adding chromiumArgs user-data-dir
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 10.5k
- Forks
- 564
- PR merge metrics
- No merged PRs in 30d
Description
Describe the bug
Hi,
npx wxt@latest init
choose Vue
npm run dev
see Chrome > Manage extensions. It shows link to inspect service worker (good)
Edit wxt.config.ts to add chromiumArgs:
import { defineConfig } from 'wxt'
export default defineConfig({
modules: ['@wxt-dev/module-vue'],
webExt: {
chromiumArgs: ['--user-data-dir=./.wxt/chrome-data'], // remember browser state between runs
},
})
npm run dev
Chrome > Manage extensions. link to inspect service worker is not shown
Reproduction
above
Steps to reproduce
above
System Info
System:
OS: Linux 6.8 Fedora Linux 38 (Workstation Edition)
CPU: (8) x64 AMD Ryzen 7 4700U with Radeon Graphics
Memory: 2.08 GB / 14.99 GB
Container: Yes
Shell: 5.2.26 - /bin/bash
Binaries:
Node: 24.9.0 - /usr/bin/node
Yarn: 1.22.22 - /usr/bin/yarn
npm: 11.6.2 - /usr/bin/npm
pnpm: 10.20.0 - /usr/bin/pnpm
Browsers:
Chrome: 141.0.7390.107
npmPackages:
wxt: ^0.20.6 => 0.20.11
Used Package Manager
npm
Validations
- Read the Contributing Guidelines.
- Read the docs.
- Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
- Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
- The provided reproduction is a minimal reproducible example of the bug.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the minimal reproduction in wxt.config.ts: add the chromiumArgs user-data-dir setting and run npm run dev, then compare Chrome's Manage extensions page with and without it. Trace the development browser launch and extension-loading entry points to identify why the service-worker inspection link disappears; done means the link remains available while browser state persists.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100