Repository navigation
Turbopack Error: Failed to write page endpoint /_error #94368
Replies: 1 comment
|
The route group itself is probably not the issue here. The biggest clue in your error report is: Normally Turbopack should detect an actual Next.js version. When it reports A few things I'd check: Verify Next.js is installednpm ls nextIf you see missing dependencies or errors, reinstall: rm -rf node_modules
rm package-lock.json
npm installCheck package.jsonMake sure {
"dependencies": {
"next": "...",
"react": "...",
"react-dom": "..."
}
}If this is a monorepoMany "Next.js package not found" errors turn out to be workspace issues. Questions I'd ask:
Try without TurbopackAs a quick diagnostic step: next devor disable Turbo temporarily and see whether the application starts normally. If it works without Turbopack, that points toward a dependency-resolution issue rather than a problem with your Check recent dependency changesI also noticed another report in this discussion involving: If you've recently:
it's worth completely removing Could you share:
The |
Uh oh!
There was an error while loading. Please reload this page.
Turbopack version:
ff756b2cNext.js version:
0.0.0Error message:
All reactions