Turbopack: Check the invalidator map before adding a path to a batch (#99711)
We don't need to add a file path to a batch and extend the batch deadline if the path isn't contained in the invalidator map. Prevents us from getting logspam like this: ``` Turbopack has seen frequent file updates and is waiting for the filesystem to settle (0.5s elapsed so far; last modified: "/Users/bgw/v0/chat/.next/dev/server/next-font-manifest.js"). ``` This is much less critical with the non-recursive watcher codepath, as we're only watching paths we might care about, but keeping it around in both cases helps ensure we get some CI coverage of this. I could put it behind `#[cfg(debug_assert)]` for non-recursive mode, IDK. --------- Co-authored-by:vercel-fleet-prod[bot] <318278635+vercel-fleet-prod[bot]@users.noreply.github.com> Co-authored-by:
Tobias Koppers <1365881+sokra@users.noreply.github.com>
Showing
This diff is collapsed.
Please
register
or
sign in
to comment