Weird interactions between `--user-data-dir`, `outDir`, and `web-ext`
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 10.5k
- Forks
- 564
- PR merge metrics
- No merged PRs in 30d
Description
Overview
I'd you use a persistent profile, and change the extension's build directory, web-ext won't update the extension installed in the profile to the new directory.
You have to fully quit Chrome or uninstall and re-run wxt for the extension path to be updated properly.
This leads to weird behaviors like entrypoints not using the latest version after saving a change and the dev server randomly crashing on MacOS after 30 seconds.
Need to pull the latest code from web-ext into my fork, web-ext-run, and investigate what's going on, and if I need to open an issue in web-ext or chrome-launcher.
Related Links
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 by reproducing the persistent-profile case while changing outDir, then inspect the integration with web-ext and web-ext-run. Check whether chrome-launcher is involved in the stale extension path or macOS crash, and use the related issues and pull request for context. Done means identifying the responsible project and either fixing the behavior or documenting a focused upstream issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system, developer-experience
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100