Skip to content

Revert "Turbopack: loader change invalidation (#95732)" - #100414

Merged
mischnic merged 4 commits into
canaryfrom
mischnic/revert-loader-invalidation
Oct 19, 2026
Merged

mischnic merged 4 commits into
canaryfrom
mischnic/revert-loader-invalidation

Conversation

@mischnic

@mischnic mischnic commented Oct 19, 2026 •

Copy link
Copy Markdown
Member

Revert part of #95732

This would cause a lot of worker pools to be created. Because get_evaluate_pool() takes as an argument the additional_invalidation and thus get a fresh worker pool per additional_invalidation

related: #100064

@mischnic
mischnic requested a review from lukesandberg October 19, 2026 17:52
@github-actions

github-actions Bot commented Oct 19, 2026 •

Copy link
Copy Markdown
Contributor

Tests Passed

Commit: b7c3ce3

@github-actions github-actions Bot added created-by: Turbopack team PRs by the Turbopack team. tests Turbopack Related to Turbopack with Next.js. type: next labels Oct 19, 2026

@vercel vercel Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Additional Suggestion:

The loaders_changed turbo_tasks function is now unused after reverting #95732 (its only call site is commented out), producing a dead_code warning that fails CI where warnings are denied.

Fix on Vercel

Comment thread test/e2e/filesystem-cache/filesystem-cache-helpers.ts Outdated
@mischnic
mischnic force-pushed the mischnic/revert-loader-invalidation branch from 9bea9fa to b7c3ce3 Compare October 19, 2026 19:17
@mischnic
mischnic merged commit 7ec769c into canary Oct 19, 2026
120 checks passed
@mischnic
mischnic deleted the mischnic/revert-loader-invalidation branch October 19, 2026 19:34
mischnic added a commit that referenced this pull request Oct 20, 2026
â€Ķ100438)

Backports #100414 to `releases/lts/active`.

Adapted the loader-change exclusions to the release branch’s unsplit
filesystem-cache suite.

<!-- NEXT_JS_LLM -->
jimmyhmiller added a commit that referenced this pull request Oct 22, 2026
1. Before the rebase, we didn't have this revert
#100414 this changed handled
stale cached results for us in certain pnpm cases. We now need to
handle these ourselves.

2. When we removed the .node special handling we exposed why it had
been hacked in there to begin with. There are times where loader deps
can be outside the repo like the .node for next. This made me revist
the whole way we were doing errors. We won't watch those files for
changes, but there is no reason to put a ton of warnings out about
them
3. Test had an edge case around shutdown that would hide a failing
test fixed that.
jimmyhmiller added a commit that referenced this pull request Oct 22, 2026
1. Before the rebase, we didn't have this revert
#100414 this changed handled
stale cached results for us in certain pnpm cases. We now need to
handle these ourselves.

2. When we removed the .node special handling we exposed why it had
been hacked in there to begin with. There are times where loader deps
can be outside the repo like the .node for next. This made me revist
the whole way we were doing errors. We won't watch those files for
changes, but there is no reason to put a ton of warnings out about
them
3. Test had an edge case around shutdown that would hide a failing
test fixed that.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

created-by: Turbopack team PRs by the Turbopack team. tests Turbopack Related to Turbopack with Next.js. type: next

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants