prime forum
thread 'tokio-runtime-worker' (9260) panicked at C:\actions-runner_work\next.js\next.js\turbopack\crates\turbo-tasks-backend\src\backend\operation\mod.rs:452:9:
Item already exists
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace
why is this happening
odd zephyrBOT
Hi @prime forum. I'm kapa.ai, your friendly support bot. I will try to answer your question by searching through the knowledge base. :wave:
I'm sorry, but the specific error message you provided:
thread 'tokio-runtime-worker' (9260) panicked at C:\actions-runner\_work\next.js\next.js\turbopack\crates\turbo-tasks-backend\src\backend\operation\mod.rs:452:9:
Item already exists
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
does not appear in any of the knowledge sources I have access to. While there are several reports of Turbopack panics and Rust errors in various parts of the codebase, none of the provided sources mention a panic specifically at operation\mod.rs:452:9 with the message "Item already exists."
Most Turbopack panics in the sources are related to issues like dynamic imports in route handlers, alias resolution, glob pattern handling, or internal bugs that are often version-specific and sometimes resolved in newer releases. In many cases, upgrading to the latest Next.js version or disabling certain experimental features (like Turbopack scope hoisting) is suggested as a workaround, but there is no direct reference to your exact error in the sources provided.
If you are encountering this error, I recommend: