Repository navigation
Turbopack Error: Cell CellId { type_id: ValueTypeId { id: 356, name: ValueType { name: "turbopack_core::issue::code_gen::CodeGenerationIssue", file_path: "(trait fn)", stage: "(trait fn)", title: "(trait fn)", description: "(trait fn)", dbg: "(trait fn)", dbg_depth: "(trait fn)" } }, index: 0 } no longer exists in task module_factory_with_code_generation_issue (no cell of this type exists) #94495
Replies: 3 comments
|
Hi, This looks like Turbopack is crashing internally while updating the app. First, I would try cleaning the cache and installing everything again: rm -rf .next
rm -rf node_modules
npm install
npm run devIf you are running the app with Turbopack, try running it without Turbopack to check if the problem is only from Turbopack: next devAlso, I noticed the Next.js version is showing as npm list nextIf the app works without Turbopack but crashes with Turbopack, then this is probably a Turbopack bug. In that case, sharing a small reproduction repo would help the maintainers debug it. Hope this helps. |
|
I encountered a similar Turbopack issue and was able to resolve it by clearing the build cache and reinstalling dependencies. The error: Cell CellId ... no longer exists in task module_factory_with_code_generation_issueusually indicates that Turbopack's internal dependency graph has become invalid after a file change, dependency update, or failed hot reload. Steps That Helped1. Stop the development serverCtrl + C2. Remove build cacherm -rf .nextWindows: rmdir /s /q .next3. Reinstall dependenciesrm -rf node_modules package-lock.json
npm installWindows: rmdir /s /q node_modules
del package-lock.json
npm install4. Verify Next.js installationnpm list nextThe reported version should be a valid Next.js version. Seeing: Next.js version: 0.0.0is unusual and may indicate an installation or dependency resolution problem. 5. Try running without Turbopacknpx next devor npm run dev -- --no-turboIf the project starts correctly, the issue is likely Turbopack-specific. 6. Check recent changesThis error can also be triggered by:
ResultAfter clearing |
|
Hi @Abdelrahamn-Fawzy-Kaoud, The Next.js version: 0.0.0 output in your log is the biggest clue here. This specific Turbopack panic (Cell CellId... no longer exists) usually happens when Turbopack's internal dependency graph becomes corrupted. Because it cannot resolve the core Next.js framework files properly (hence the 0.0.0 version), the compiler crashes when trying to generate the code. To fix this, you need to completely nuke the corrupted local environment and force a fresh resolution of your packages. Here is the most reliable way to clear this up:
Bash For Mac/Linuxrm -rf .next node_modules package-lock.json For Windowsrmdir /s /q .next node_modules Bash
Bash Let me know if a clean install gets it running for you! |
Uh oh!
There was an error while loading. Please reload this page.
Turbopack version:
23c46498Next.js version:
0.0.0Error message:
All reactions