Repository navigation
Turbopack Error: Failed to write app endpoint /compare/page #94437
Replies: 1 comment
|
This particular message looks more like a stale/invalidated Turbopack incremental graph than a missing The clue is: Cell ... no longer exists in task ... directory_tree_to_loader_treeThat sounds like Turbopack had an old task/cell in its dev graph and then tried to use it after the route tree changed. Since Turbopack is incremental and caches work between dev runs, I would start with a true cold restart: # stop next dev first
rm -rf .next
npm run devOn Windows PowerShell: # stop next dev first
Remove-Item -Recurse -Force .next
npm run devIf it happens again after a clean
npm ls nextThe generated report says
npm run dev -- --webpack
# or
npx next dev --webpackNext 16 uses Turbopack by default, and the docs note that webpack is still available through the
npx next internal trace .next/dev/trace-turbopackThat trace will be much more actionable for the maintainers than the stack alone. So my first practical fix would be clearing |
Uh oh!
There was an error while loading. Please reload this page.
Turbopack version:
ee6e79b1Next.js version:
0.0.0Error message:
All reactions