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:1526:13

[VasilKostadinov0104]

Turbopack version: 23c464985
Next.js version: 0.0.0

Error message:

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:1526:13

[thangsauce]

Hey Vasi!

This looks like a Turbopack internal error, not a normal app code error. A bunch of similar reports have been filed for the exact message Dependency tracking is disabled so invalidation is not allowed, including on recent Next.js 16.x / Turbopack builds.

The most useful thing I found is that this often ends up being caused by duplicate metadata files in the app/ directory, especially icon files with the same base name. One confirmed example was having both app/icon.png and app/icon.ico; removing one fixed the build. There’s also a tracked Next.js issue for Turbopack failing when multiple app/ icons have the same name.

I’d check these first:

app/icon.png + app/icon.ico
app/icon.png + app/icon.svg
app/apple-icon.png + another apple-icon.*

Next.js treats icon, apple-icon, and favicon as special metadata file conventions, so conflicts there can confuse the compiler.

What I’d try:

In app/, keep only one icon.* file for each special metadata name.
Move extra icons/images to public/ if you still need them.
Delete .next and restart the dev/build process.

Example:

rm -rf .next
npm run dev

or

npm run build

So in short: this is probably not your page code itself. I’d start by checking for duplicate special metadata files under app/, because that has fixed this exact Turbopack panic for other people.

Lmk if you need anymore help!