Skip to content

Commit 5fcbc45

Browse files
committed
chore: bump #295 changeset to major and document the breaking behavior change
The fix changes which initial-scan `change` events fire for files created within `FS_ACCURACY` of `startTime`. Downstream consumers (including webpack) may have been observing those events to invalidate caches; mark the changeset accordingly. https://claude.ai/code/session_01CfqWhrftEvFkN5GiG82P67
1 parent 1d32615 commit 5fcbc45

1 file changed

Lines changed: 8 additions & 1 deletion

File tree

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

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

55
fix: do not emit spurious initial-scan `change` events for files and
@@ -18,3 +18,10 @@ 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)