Turbopack Error: Cell CellId { type_id: ValueTypeId { id: 8, name: "turbo-tasks@TODO::::effect::EffectInstance" }, index: 0 } no longer exists in task <DiskFileSystem as FileSystem>::write (no cell of this type exists)

[aarondill]

Turbopack version: 6ac83a20
Next.js version: 0.0.0

Error message:

Cell CellId { type_id: ValueTypeId { id: 8, name: "turbo-tasks@TODO::::effect::EffectInstance" }, index: 0 } no longer exists in task <DiskFileSystem as FileSystem>::write (no cell of this type exists)

Debug info:
- Execution of hmr_update_with_issues_operation failed
- Cell CellId { type_id: ValueTypeId { id: 8, name: "turbo-tasks@TODO::::effect::EffectInstance" }, index: 0 } no longer exists in task <DiskFileSystem as FileSystem>::write (no cell of this type exists)

next-panic-6f00db77f9b5641242901562834d9dea.log

[SametDulger]

I’ve seen this error pop up in a few recent Turbopack builds — it seems related to internal task/cell invalidation in the file system write layer. The reference to EffectInstance and the ::write task suggests something went wrong during hot module reloading (HMR), possibly due to an outdated or corrupted internal state.

A few things you could try:

1. Clear the Turbopack cache
   Sometimes stale caches can cause issues like this. Try removing the .next directory:

rm -rf .next

2. Clean reinstall
   Reinstalling dependencies and starting fresh might help:

rm -rf node_modules
rm package-lock.json
npm install

3. Update to the latest Next.js / Turbopack
   You’re currently on [email protected], which might be a placeholder or incorrect version. Make sure your next version is up to date, and that you're using a stable build of Turbopack.

If the issue persists, it might help to share steps to reproduce or confirm if it happens in a clean environment. Looks like an internal cell/task mapping issue that could be valuable for the Turbopack team to trace further.

[aarondill]

I just restarted the server and it worked without further issue. my next version is 15.4.5. I was only reporting in case the stack trace helped to fix a bug