fix(webpack): disable static directory watcher to prevent watching entire workspace #10116
+10
−6
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.
When webpack-dev-server's static directory watcher is enabled but the directory doesn't exist (which is typically the case), Chokidar recursively walks up the directory tree to find an existing parent to watch. This causes it to watch the entire workspace root directory, triggering unnecessary file system events on every file change.
Investigation findings:
preview/teambit.harmony/node/publicdon't exist/tmp/workspace)Changes:
watch: truein both webpack dev configs (webpack/config/webpack.dev.config.tsandui-foundation/ui/webpack/webpack.dev.config.ts)Static files rarely change during development, and if they do, a server restart is acceptable.