Skip to content

Fix watch coalescing for FSEvents#4379

Draft
jakebailey wants to merge 4 commits into
mainfrom
jabaile/fix-4378
Draft

Fix watch coalescing for FSEvents#4379
jakebailey wants to merge 4 commits into
mainfrom
jabaile/fix-4378

Conversation

@jakebailey

Copy link
Copy Markdown
Member

Fixes #4378

Coalesce dense directory watch sets into recursive ancestor watches on fast-recursive backends such as FSEvents and Windows. This avoids opening one stream per dependency directory while still surfacing startup failures.

Coalesce dense directory watch sets into recursive ancestor watches on
fast-recursive backends such as FSEvents and Windows. This avoids
opening one stream per dependency directory while still surfacing
startup failures.
@jakebailey

Copy link
Copy Markdown
Member Author

This is doing this in the layer above fswatch, but, going to try and shove it down...

Consolidate dense directory subscriptions inside fswatch for fast
recursive backends. Parent streams now serve later child subscriptions
with per-subscriber filtering, so all fswatch callers benefit without
watch-manager-specific planning.
Add a tsc watch integration baseline covering many dependency files
under a Bun-style node_modules/.bun layout. The lower-level fswatch
tests assert stream coalescing; this keeps the command-line watch shape
covered end-to-end.
# Conflicts:
#	internal/fswatch/watcher.go
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

tsgo --watch error: "error starting FSEvents stream" on large node_modules since the fswatch rewrite

1 participant