Next 16.0.7 - Turbopack Error: Dependency tracking is disabled so invalidation is not allowed at C:\actions-runner\_work\next.js\next.js\turbopack\crates\turbo-tasks-backend\src\....... #86943
Replies: 3 comments 1 reply
-
|
How do I publish the project when a security patch is required - it now doesn't generate output files in the folder :/ |
Beta Was this translation helpful? Give feedback.
-
|
I don't get it |
Beta Was this translation helpful? Give feedback.
-
|
I executed: Then I rewrote the package.json, all the .mjs files, copied the entire /src/, and... it started working. Before that, I tried installing, updating, and changing the version, and nothing helped. strange as * but working now |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi
I got this, after first 'npm run build", after last updae to Next "16.0.7". The previous version worked fine
So now I don't know what's going on :?
Turbopack version:
b1a04a84Next.js version:
0.0.0Error message:
▲ Next.js 16.0.7 (Turbopack)
Creating an optimized production build ...
thread 'tokio-runtime-worker' (39256) panicked at C:\actions-runner_work\next.js\next.js\turbopack\crates\turbo-tasks-backend\src\backend\mod.rs:1523:13:
Dependency tracking is disabled so invalidation is not allowed
note: run with
RUST_BACKTRACE=1environment variable to display a backtracethread 'tokio-runtime-worker' (39432) panicked at C:\actions-runner_work\next.js\next.js\turbopack\crates\turbo-tasks-backend\src\backend\mod.rs:1523:13:
Dependency tracking is disabled so invalidation is not allowed
FATAL: An unexpected Turbopack error occurred. A panic log has been written to C:\Users..AppData\Local\Temp\next-panic-35cbf91fd4898bece90fe64ef59d17ee.log.
To help make Turbopack better, report this error by clicking here.
Beta Was this translation helpful? Give feedback.
All reactions