nuxt
cli
BlogDocsChangelog

fix(dev): prime mtimes cache when starting dev server

#1137Merged
Comparing
aroneous:fix/1135-mtimes
(
7c3db44
) with
main
(
b04de4f
)
CodSpeed Performance Gauge
0%
Untouched
2

Benchmarks

Passed

makes requests to dev server
packages/nuxt-cli/test/bench/dev.bench.ts::dev [linux]
CodSpeed Performance Gauge
0%
55.5 ms55.6 ms
starts dev server with --no-fork
packages/nuxt-cli/test/bench/dev.bench.ts::dev [linux]
CodSpeed Performance Gauge
-1%
231.8 ms233.4 ms

Commits

Click on a commit to change the comparison range
Base
main
b04de4f
+0.96%
fix(dev): Prime mtimes cache When watching for file/directory changes, prime the FileChangeTracker with initial mtimes of the tracked files, such that if the first notification received for a file is spurious (does not represent an actual change), shouldEmitChange will return 'false'. Without this, the 'priming' happened via several reloads/restarts, but with the introduction of the ForkPool, the FileChangeTracker cache no longer perists across restarts, never allowing it to become populated. Result: unpredictable restarts.
25012a1
19 days ago
by aroneous
-0.48%
[autofix.ci] apply automated fixes
4e5c06d
19 days ago
by autofix-ci[bot]
-0.48%
Normalize path separators for Windows Pass all paths through `resolve` to ensure consistent path separators on Windows.
cc046e1
19 days ago
by aroneous
+4.62%
Merge branch 'main' into fix/1135-mtimes
50f1b84
6 days ago
by danielroe
-0.25%
test: specify bun dev server starts on windows
0ec1a80
6 days ago
by danielroe
-4.81%
Merge remote-tracking branch 'origin/main' into fix/1135-mtimes
7c3db44
6 days ago
by danielroe
© 2025 CodSpeed Technology
Home Terms Privacy Docs