FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-da8431fdb961198c2c41186f79b7b442.log.

To help make Turbopack better, report this error by clicking here: https://github.com/vercel/next.js/discussions/new?category=turbopack-error-report&title=Turbopack%20Error%3A%20Invalid%20distDirRoot%3A%20%22.next%22.%20distDirRoot%20should%20not%20navigate%20out%20of%20the%20projectPath.&body=Turbopack%20version%3A%20%60d1bd5b58%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Invalid%20distDirRoot%3A%20%22.next%22.%20distDirRoot%20should%20not%20navigate%20out%20of%20the%20projectPath.%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace

Error [TurbopackInternalError]: Invalid distDirRoot: ".next". distDirRoot should not navigate out of the projectPath.

Debug info:

• Execution of Project::project_fs failed
• Invalid distDirRoot: ".next". distDirRoot should not navigate out of the projectPath. at <unknown> (TurbopackInternalError: Invalid distDirRoot: ".next". distDirRoot should not navigate out of the projectPath.) { location: undefined }

TL;DR

The issue can be resolved by configuring the distDir option in the Next.js configuration to a valid directory that does not navigate out of the project path.

Guidance

• Verify the next.config.js file for any custom configurations that might be causing the distDirRoot to be set to .next, which is not a valid directory.
• Check the project structure to ensure that the .next directory is not being used as a build output directory.
• Update the next.config.js file to include a valid distDir option, such as distDir: 'build', to specify the build output directory.
• Run npm run build again to test if the issue is resolved.

Example

No code example is provided as the issue is related to configuration and not a specific code snippet.

Notes

The issue seems to be related to the distDirRoot configuration in Turbopack, which is used by Next.js. The error message indicates that the .next directory is not a valid build output directory. The solution involves updating the next.config.js file to specify a valid build output directory.

Recommendation

Apply workaround: Update the next.config.js file to include a valid distDir option, such as distDir: 'build', to specify the build output directory. This should resolve the issue with Turbopack panicking due to an internal error.