nextjs - 💡(How to fix) Fix Turbopack: Build error when importing Turborepo monorepo package dependency which uses `next/dynamic` into meta files (`robots.ts`, `sitemap.ts`) [2 comments, 2 participants]

next build --turbopack

▲ Next.js 15.5.0 (Turbopack)

Creating an optimized production build ...

thread 'tokio-runtime-worker' panicked at crates/next-api/src/dynamic_imports.rs:70:26: called Option::unwrap() on a None value note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

FATAL: An unexpected Turbopack error occurred. A panic log has been written to /var/folders/vh/r5pbsmwn4f37ch9153sj297w000 0gn/T/next-panic-429073751881a9b45a867bcd3c5143c5.log.

To help make Turbopack better, report this error by clicking here.

Build error occurred Error [TurbopackInternalError]: Failed to write app endpoint /robots.txt/route

Caused by:

• called Option::unwrap() on a None value

Debug info:

• Execution of TaskId { id: 2147483650 } transient failed
• Execution of get_all_written_entrypoints_with_issues_operation failed
• Execution of EntrypointsOperation::new failed
• Execution of all_entrypoints_write_to_disk_operation failed
• Execution of Project::emit_all_output_assets failed
• Execution of *emit_assets failed
• Execution of all_assets_from_entries_operation failed
• Execution of *all_assets_from_entries failed
• Execution of output_assets_operation failed
• Execution of <AppEndpoint as Endpoint>::output failed
• Failed to write app endpoint /robots.txt/route
• Execution of AppEndpoint::output failed
• called Option::unwrap() on a None value at <unknown> (TurbopackInternalError: Failed to write app endpoint /robots.txt/route) { type: 'TurbopackInternalError', location: 'crates/next-api/src/dynamic_imports.rs:70:26' }

TL;DR

The build error is likely due to an issue with Turbopack in Next.js 15.5.0, and a potential workaround is to try disabling Turbopack or checking for any configuration issues.

Guidance

• Check the next.config.js file for any custom configurations that might be causing the issue with Turbopack.
• Try running the build command with the --no-turbopack flag to disable Turbopack and see if the build succeeds.
• Verify that the robots.txt file is correctly configured and not causing any issues with the build process.
• Consider reporting the issue to the Next.js team, as the error message suggests, to help improve Turbopack.

Notes

The issue seems to be related to Turbopack, and the error message provides a specific location in the code where the error occurs. However, without more information about the project's configuration and code, it's difficult to provide a more specific solution.

Recommendation

Apply workaround: Try disabling Turbopack or checking for any configuration issues, as this might resolve the build error.