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:1477:13 #84585

codercatdev · 2025-10-07T00:42:55Z

codercatdev
Oct 7, 2025

Turbopack version: v15.6.0-canary.40-2-g09bdc4523
Next.js version: 15.6.0-canary.41

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

brian-bourdon · 2025-10-10T20:23:05Z

brian-bourdon
Oct 10, 2025

same error when upgrading from 15.5.4 to 16.0.0 beta:

Turbopack version: v16.0.0-beta.0
Next.js version: 0.0.0

Error message:

Dependency tracking is disabled so invalidation is not allowed at /build/turbopack/crates/turbo-tasks-backend/src/backend/mod.rs:1477:13

0 replies

arioberek · 2025-10-12T22:14:51Z

arioberek
Oct 12, 2025

Same happened to me upgrading from 15.5.4 to 16.0.0 beta

Turbopack version: v16.0.0-beta
Next.js version: 0.0.0

Error message:

Dependency tracking is disabled so invalidation is not allowed at /build/turbopack/crates/turbo-tasks-backend/src/backend/mod.rs:1477:13

0 replies

lukesandberg · 2025-10-12T22:38:11Z

lukesandberg
Oct 12, 2025
Maintainer

Do you have a repro? I assume this happened in the context of a next build command?

1 reply

arioberek Oct 12, 2025

Not yet. It happens in next build --turbopack (Next 16.0.0-beta.0 and 16.0.0-canary.2). Reproducible locally and on Vercel. Node 22.18, pnpm, Ubuntu. Panic:

TurbopackInternalError: Dependency tracking is disabled so invalidation is not allowed
/build/turbopack/crates/turbo-tasks-backend/src/backend/mod.rs:1477:13
What I tried to reproduce in a minimal repo but couldn’t:

Fresh Next 16 beta app with --turbopack build → passes.

Added Sentry, instrumentation.ts, and removed deprecated experimental.instrumentationHook → still passes.

Imported code from src/shared into src/app, then CSS modules and SVG from that shared folder → passes.

Introduced a local workspace/lib via file: dep and path aliases → passes.

Flipped turbopack.root between app dir and monorepo root, matched with/without outputFileTracingRoot, cleared caches, reinstalled → passes. (Docs say files outside the root aren’t resolved and the root is inferred from lockfiles, so I aligned to that.)

P.S.:

Ran with RUST_BACKTRACE=full and other verbose flags. Output showed only opaque frames like:

     Dependency tracking is disabled so invalidation is not allowed
     stack backtrace:
        0:     0x74b32d9680b2 - <unknown>
        1:     0x74b32d97c98f - <unknown>
        2:     0x74b32d932c31 - <unknown>
        3:     0x74b32d940cc2 - <unknown>
        4:     0x74b32d94770c - <unknown>
        5:     0x74b32d947566 - <unknown>
        6:     0x74b32d947dcf - <unknown>
        7:     0x74b32d947bf6 - <unknown>
        8:     0x74b32d940e09 - <unknown>
        9:     0x74b32d925b9d - <unknown>
       10:     0x74b32865d150 - <unknown>
       11:     0x74b3289ec696 - <unknown>
       12:     0x74b32885bc29 - <unknown>
       13:     0x74b32c34c454 - <unknown>
       14:     0x74b32c30e6c2 - <unknown>
       15:     0x74b32c374172 - <unknown>
       16:     0x74b32aec90b3 - <unknown>
       17:     0x74b32af30c58 - <unknown>
       18:     0x74b32aec8c5a - <unknown>
       19:     0x74b32af1335b - <unknown>
       20:     0x74b32af0a846 - <unknown>
       21:     0x74b32af1284d - <unknown>
       22:     0x74b32af12a24 - <unknown>
       23:     0x74b32d919594 - <unknown>
       24:     0x74b32d918c10 - <unknown>
       25:     0x74b32d8eaf18 - <unknown>
       26:     0x74b32d8f0699 - <unknown>
       27:     0x74b32d919b62 - <unknown>
       28:     0x74b32d8e6eed - <unknown>
       29:     0x74b32d8e1f98 - <unknown>
       30:     0x74b32d8d62c1 - <unknown>
       31:     0x74b32d8d72c6 - <unknown>
       32:     0x74b32d8e5178 - <unknown>
       33:     0x74b32d8fed94 - <unknown>
       34:     0x74b32d908541 - <unknown>
       35:     0x74b32d8e8e92 - <unknown>
       36:     0x74b32d93bd4f - <unknown>
       37:     0x74b84d8a27f1 - start_thread
                                    at ./nptl/pthread_create.c:448:8
       38:     0x74b84d933b5c - __GI___clone3
                                    at ./misc/../sysdeps/unix/sysv/linux/x86_64/clone3.S:78:0
       39:                0x0 - <unknown>

     thread 'tokio-runtime-worker' (489666) panicked at /build/turbopack/crates/turbo-tasks-backend/src/backend/mod.rs:1477:13:
     Dependency tracking is disabled so invalidation is not allowed
     stack backtrace:
        0:     0x74b32d9680b2 - <unknown>
        1:     0x74b32d97c98f - <unknown>
        2:     0x74b32d932c31 - <unknown>
        3:     0x74b32d940cc2 - <unknown>
        4:     0x74b32d94770c - <unknown>
        5:     0x74b32d947566 - <unknown>
        6:     0x74b32d947dcf - <unknown>
        7:     0x74b32d947bf6 - <unknown>
        8:     0x74b32d940e09 - <unknown>
        9:     0x74b32d925b9d - <unknown>
       10:     0x74b32865d150 - <unknown>
       11:     0x74b3289ec696 - <unknown>
       12:     0x74b32885bc29 - <unknown>
       13:     0x74b32c34c454 - <unknown>
       14:     0x74b32c30e6c2 - <unknown>
       15:     0x74b32c374172 - <unknown>
       16:     0x74b32aec90b3 - <unknown>
       17:     0x74b32af30c58 - <unknown>
       18:     0x74b32aec8c5a - <unknown>
       19:     0x74b32af1335b - <unknown>
       20:     0x74b32af0a846 - <unknown>
       21:     0x74b32af1284d - <unknown>
       22:     0x74b32af12a24 - <unknown>
       23:     0x74b32d919594 - <unknown>
       24:     0x74b32d918c10 - <unknown>
       25:     0x74b32d8eaf18 - <unknown>
       26:     0x74b32d8f0699 - <unknown>
       27:     0x74b32d919b62 - <unknown>
       28:     0x74b32d8e6eed - <unknown>
       29:     0x74b32d8e1f98 - <unknown>
       30:     0x74b32d8d62c1 - <unknown>
       31:     0x74b32d8d72c6 - <unknown>
       32:     0x74b32d8e5178 - <unknown>
       33:     0x74b32d8fed94 - <unknown>
       34:     0x74b32d908541 - <unknown>
       35:     0x74b32d8e8e92 - <unknown>
       36:     0x74b32d93bd4f - <unknown>
       37:     0x74b84d8a27f1 - start_thread
                                    at ./nptl/pthread_create.c:448:8
       38:     0x74b84d933b5c - __GI___clone3
                                    at ./misc/../sysdeps/unix/sysv/linux/x86_64/clone3.S:78:0
       39:                0x0 - <unknown>

     -----

arioberek · 2025-10-21T13:14:07Z

arioberek
Oct 21, 2025

Any updates on this?

0 replies

paschun · 2025-10-22T05:24:21Z

paschun
Oct 22, 2025

I have this error in v16.0.0. Here's the backtrace

thread 'tokio-runtime-worker' (1457314) panicked at /Users/jj/dev/actions-runner/_work/next.js/next.js/turbopack/crates/turbo-tasks-backend/src/backend/mod.rs:1514:13:
Dependency tracking is disabled so invalidation is not allowed
stack backtrace:
   0:        0x143c5e5ac - _napi_register_module_v1
   1:        0x143c70264 - _napi_register_module_v1
   2:        0x143c32594 - _napi_register_module_v1
   3:        0x143c3cea0 - _napi_register_module_v1
   4:        0x143c41e54 - _napi_register_module_v1
   5:        0x143c41d08 - _napi_register_module_v1
   6:        0x143c42688 - _napi_register_module_v1
   7:        0x143c4230c - _napi_register_module_v1
   8:        0x143c3cfb8 - _napi_register_module_v1
   9:        0x143c2a428 - _napi_register_module_v1
  10:        0x143d9bf44 - _napi_register_module_v1
  11:        0x13f1bf6ec - <unknown>
  12:        0x13f1f95a0 - <unknown>
  13:        0x1428a741c - _BrotliDecoderVersion
  14:        0x1427f5088 - _BrotliDecoderVersion
  15:        0x14281d014 - _BrotliDecoderVersion
  16:        0x1414788f4 - _BrotliDecoderVersion
  17:        0x1414a9b5c - _BrotliDecoderVersion
  18:        0x14147866c - _BrotliDecoderVersion
  19:        0x1414d677c - _BrotliDecoderVersion
  20:        0x1414cda44 - _BrotliDecoderVersion
  21:        0x1414d5bb0 - _BrotliDecoderVersion
  22:        0x1414d5db4 - _BrotliDecoderVersion
  23:        0x143c1a264 - _napi_register_module_v1
  24:        0x143c196cc - _napi_register_module_v1
  25:        0x143bec69c - _napi_register_module_v1
  26:        0x143be850c - _napi_register_module_v1
  27:        0x143c1a8e4 - _napi_register_module_v1
  28:        0x143c0d5f4 - _napi_register_module_v1
  29:        0x143c009d8 - _napi_register_module_v1
  30:        0x143bde31c - _napi_register_module_v1
  31:        0x143bdf0f8 - _napi_register_module_v1
  32:        0x143c0b784 - _napi_register_module_v1
  33:        0x143c1fdbc - _napi_register_module_v1
  34:        0x143bf608c - _napi_register_module_v1
  35:        0x143bf0c60 - _napi_register_module_v1
  36:        0x143c3a2c0 - _napi_register_module_v1
  37:        0x18cb74c08 - __pthread_cond_wait

> Build error occurred
Error [TurbopackInternalError]: Dependency tracking is disabled so invalidation is not allowed at /Users/jj/dev/actions-runner/_work/next.js/next.js/turbopack/crates/turbo-tasks-backend/src/backend/mod.rs:1514:13
    at <unknown> (TurbopackInternalError: Dependency tracking is disabled so invalidation is not allowed at /Users/jj/dev/actions-runner/_work/next.js/next.js/turbopack/crates/turbo-tasks-backend/src/backend/mod.rs:1514:13) {
  type: 'TurbopackInternalError',
  location: '/Users/jj/dev/actions-runner/_work/next.js/next.js/turbopack/crates/turbo-tasks-backend/src/backend/mod.rs:1514:13'
}

0 replies

samoyedisco · 2025-10-23T16:14:18Z

samoyedisco
Oct 23, 2025

Here is a potential solution, please let me know if it was helpful for you: #85232 (comment)

0 replies

paschun · 2025-11-04T21:37:35Z

paschun
Nov 4, 2025

Opened an issue: #85496

0 replies

nextjs-bot · 2026-01-15T21:44:40Z

nextjs-bot
Jan 15, 2026
Maintainer

20 duplicate discussions were consolidated into this one:

Combined engagement from duplicates: 30 upvotes, 5 comments

This comment was added automatically by discussion consolidation tool.

0 replies

alihatem361 · 2026-01-25T13:15:12Z

alihatem361
Jan 25, 2026

I faced the exact same issue (Turbopack panic: Dependency tracking is disabled) during deployment on Vercel.

For anyone stuck in this loop, I managed to get a successful build by prioritizing stability. I also discovered a silent "BOM Encoding" issue that was causing JSON parse errors.

Here is the full solution that worked for me:

Reverted to Next.js 14 (LTS): Since Next.js 16 with Turbopack seems unstable for production builds on Vercel right now, I downgraded to 14.2.35 to use Webpack.
Fixed ESLint Conflicts: Downgraded ESLint to ^8.57.0 to match eslint-config-next.
The "Silent" Bug (UTF-8 BOM): If you are modifying files via PowerShell on Windows, be careful. It might add a BOM (Byte Order Mark) to the beginning of your package.json, causing Vercel to throw SyntaxError: Unexpected token. Make sure to save your files as UTF-8 (No BOM).

Here is the working package.json configuration:

{
  "scripts": {
    "dev": "next dev",
    "build": "next build",
    "start": "next start",
    "lint": "eslint"
  },
  "dependencies": {
    "next": "14.2.35",
    "react": "^18.3.1",
    "react-dom": "^18.3.1"
  },
  "devDependencies": {
    "eslint": "^8.57.0",
    "eslint-config-next": "14.2.35"
  }
}

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

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:1477:13 #84585

Uh oh!

{{title}}

Uh oh!

Replies: 9 comments 1 reply

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

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:1477:13 #84585

Uh oh!

Replies: 9 comments · 1 reply

Uh oh!

Uh oh!

Uh oh!

lukesandberg Oct 12, 2025 Maintainer

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

nextjs-bot Jan 15, 2026 Maintainer

Uh oh!

Replies: 9 comments 1 reply

lukesandberg
Oct 12, 2025
Maintainer

nextjs-bot
Jan 15, 2026
Maintainer