Skip to content

Commit 7d301fc

Browse files
committed
chore: revert #295 changeset to patch
The fix aligns behavior with the documented "watching can be started in the past" semantics. The previously-spurious initial-scan events were undocumented and surprising (as the issue itself notes), so the realistic risk of breaking a downstream consumer that relied on them is low — patch is the right level. https://claude.ai/code/session_01CfqWhrftEvFkN5GiG82P67
1 parent 5fcbc45 commit 7d301fc

1 file changed

Lines changed: 1 addition & 8 deletions

File tree

‎.changeset/fix-startime-fs-accuracy.md‎

Lines changed: 1 addition & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,5 @@
11
---
2-
"watchpack": major
2+
"watchpack": patch
33
---
44

55
fix: do not emit spurious initial-scan `change` events for files and
@@ -18,10 +18,3 @@ The `startTime` filter now compares against the raw `mtime`/`birthtime`
1818
instead, so only entries actually modified at or after `startTime`
1919
trigger a change event. The `change` event payload (and the existing
2020
`safeTime` semantics for consumers) are unchanged.
21-
22-
**Breaking change:** consumers that relied on receiving initial-scan
23-
`change` events for files created within `FS_ACCURACY` of `startTime`
24-
(for example, to invalidate caches for files that were touched
25-
immediately before watching began) will no longer receive those events.
26-
The "outdated on attach" code path in `watch()` is unaffected and still
27-
uses `safeTime` semantics.

0 commit comments

Comments
 (0)