feat(wxt): expose file watcher options#2398
Open
myjeong19 wants to merge 1 commit into
Open
Conversation
✅ Deploy Preview for creative-fairy-df92c4 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Overview
Adds a
watchOptionsconfig option towxt.config.tsso users can configure file watching behavior.This is intended for environments where native file events may not be delivered reliably, such as Docker, devcontainers, WSL mounts, or network filesystems. In those cases, users can opt into polling with
watchOptions: { usePolling: true }instead of relying onCHOKIDAR_USEPOLLING=1.The options are forwarded to Vite's dev server watcher while preserving WXT's default ignored paths.
Manual Testing
Run the dev server e2e test
bun run --filter wxt test -- --run e2e/tests/dev.test.tsThis verifies that
watchOptionsis forwarded to Vite's dev server watcher while preservingusePolling,interval, WXT's default ignored paths, existingvite.server.watch, and custom ignored entries.Docker & Dev Container manual checks
To manually verify the behavior, run a WXT project with:
inside a Docker container or devcontainer, edit a mounted source file from inside the same container, and confirm that WXT logs the change and reloads the extension.
I also tested this branch in both a Docker container and a VS Code devcontainer with
packages/wxt-demousing a temporarywatchOptions: { usePolling: true, interval: 1000 }config. Editing an entrypoint file from inside the same container triggered reload in both cases.Related Issue
This PR closes #2342