Issue Station
Sign In
Tools hereToolbox

nextjs - 💡(How to fix) Fix [Turbopack] Runtime panic in aggregation_update.rs when running dev server [2 comments, 3 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
vercel/next.js#84096•Fetched 2026-04-08 02:20:35
View on GitHub
Comments
2
Participants
3
Timeline
7
Reactions
0
Author
APSK22APSK22
Participants
APSK22APSK22github-actions[bot]github-actions[bot]mischnicmischnic
Timeline (top)
commented ×2labeled ×2closed ×1issue_type_added ×1

Error Message

  1. Server crashes with aggregation_update.rs panic error Actual: The development server panics with a Rust error:
  • Error location: Internal Turbopack task management (aggregation_update.rs:1572:17)

Code Example

Operating System:
  Platform: darwin
  Arch: arm64
  Version: macOS (Darwin Kernel)
Binaries:
  Node: 22.12.0
  npm: 10.9.0
Relevant Packages:
  next: 15.2.0
  eslint-config-next: 15.1.6
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5
RAW_BUFFERClick to expand / collapse

Link to the code that reproduces this issue

https://github.com/APSK22/vibe-check

To Reproduce

  1. Start the application in development with Turbopack (npm run dev or next dev --turbopack)
  2. The development server attempts to start
  3. Rust panic occurs in turbopack task management system
  4. Server crashes with aggregation_update.rs panic error

Current vs. Expected behavior

Expected: The development server should start successfully with Turbopack enabled and run without crashing.

Actual: The development server panics with a Rust error:

Provide environment information

Operating System:
  Platform: darwin
  Arch: arm64
  Version: macOS (Darwin Kernel)
Binaries:
  Node: 22.12.0
  npm: 10.9.0
Relevant Packages:
  next: 15.2.0
  eslint-config-next: 15.1.6
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5

Which area(s) are affected? (Select all that apply)

Turbopack

Which stage(s) are affected? (Select all that apply)

next dev (local)

Additional context

  • Issue occurs: Only when using --turbopack flag
  • Deployment: Local development only, not affecting production builds
  • Project type: React/Next.js with TypeScript, MUI, Tailwind CSS
  • Reproducibility: Consistent on macOS with Node.js 22.12.0
  • Error location: Internal Turbopack task management (aggregation_update.rs:1572:17)
  • Temporary solution: Removing --turbopack flag allows normal development

extent analysis

TL;DR

  • The most likely fix is to avoid using the --turbopack flag until the underlying issue with Turbopack's task management system is resolved.

Guidance

  • Investigate the compatibility of Turbopack with the current project setup, especially considering the versions of Next.js, Node.js, and other dependencies.
  • Verify if the issue persists when using a different version of Node.js or when updating Next.js and its related packages to the latest versions.
  • Consider filing an issue with the Turbopack project if the problem seems to be related to its internal task management, referencing the aggregation_update.rs error.
  • As a temporary workaround, remove the --turbopack flag to allow for normal development, as indicated in the additional context.

Example

  • No specific code snippet can be provided without more details on the custom codebase, but ensuring that all dependencies are up-to-date might help mitigate the issue.

Notes

  • The solution might depend on the specific versions of the packages and the operating system used, as the issue seems to be reproducible only on macOS with Node.js 22.12.0.
  • There's a limitation in providing a definitive fix without more information on the Turbopack version and its compatibility with the project's setup.

Recommendation

  • Apply workaround: Remove the --turbopack flag for development purposes until a more permanent solution or fix is available for the Turbopack issue.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…
#SSR setup#ISR setup#authentication setup#request error#file not found

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING