PollWatcher: detect subsecond mtime changes - #981
Merged
JohnTitor merged 3 commits intoAug 17, 2026
Conversation
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
2 participants
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.
Description
PollWatcher stores file modification times at whole-second precision. When content comparison is disabled, multiple writes within the same second compare equal and the later write produces no event.
This keeps nanosecond precision for ordinary files so those writes are detected. Directories and content-hashed watches retain their previous whole-second behavior to avoid redundant directory events and preserve existing event classification.
A regression test advances a file mtime twice within one second and verifies a WriteTime event is emitted without content hashing.
Related Issues
watchOptions.pollIntervalMspermanently drops file edits on Windows vercel/next.js#96982