Hendrik LiebauandGitHub e1fbb1800f Run dev validation in process when using Webpack (#96219) ...

Node.js caches source maps per isolate, so the dev validation worker
only has maps for the chunk files loaded on its own thread. For chunks
it never loads, such as a module behind a dynamic `import()`, it reads
the `.map` that Turbopack writes next to the chunk. Webpack keeps its
dev source maps in the compiler instead, so the worker has nothing to
read and reports those frames with the position they have in the
compiled output rather than in the source.

This stops using the worker when the bundler is Webpack, so validation
runs in process again, where those frames resolve, and
`experimental.devValidationWorker` now has no effect there. Dev
performance under Webpack goes back to what it was before validation
moved to a worker, which is the better trade: the worker exists to keep
the event loop responsive during rapid navigation, and that is not worth
losing the source location on validation errors.

2026-07-25 16:30:39 +02:00

..

app

…

dev-validation-worker-source-maps.test.ts

Run dev validation in process when using Webpack (#96219)

2026-07-25 16:30:39 +02:00

next.config.js

…