Turbopack Error: Dependency tracking is disabled so invalidation is not allowed at /Users/geist/dev/actions-runner/_work/next.js/next.js/turbopack/crates/turbo-tasks-backend/src/backend/mod.rs:1523:13 #86193
Replies: 5 comments 4 replies
-
|
this error basically happens when turbopack is running in a place where it can’t track dependencies (like inside actions-runner folders). it tries to invalidate something and just panics the path in your logs: quick fixes u can try:
this is a known turbopack issue btw, nothing wrong with prisma or your code. it’s just turbopack panicking when dependency tracking is off. building outside the runner or turning off turbopack fixes it |
Beta Was this translation helpful? Give feedback.
-
|
Hey there! I'm getting the exact same error, down to the path ( I just want to be clear (in reference to your first and fourth comment) that this issue is happening even when not in any kind of runner environment. |
Beta Was this translation helpful? Give feedback.
-
|
Had the same issue after updating to Next.js 16, both locally (M1 MacBook) and on Vercel. Saw this issue #85496 and deleting all but one |
Beta Was this translation helpful? Give feedback.
-
|
Looks like the simmilar issue, but now with latest release of Next.js 16.1.1 production builds fail with a Turbopack panic: Environment
Details |
Beta Was this translation helpful? Give feedback.
-
|
This discussion appears to be a duplicate of #85232. Please follow the discussion there: #85232 This comment was added automatically by the discussion consolidation tool. If you believe this is in error, feel free to re-open the discussion. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Turbopack version:
a51b80449Next.js version:
16.0.3Error message:
Beta Was this translation helpful? Give feedback.
All reactions