[email protected] build /home/arunb/work-related/safedep-related/safedep.io-next next build --turbopack

⚠ Invalid next.config.ts options detected: ⚠ Unrecognized key(s) in object: 'conditions' at "turbopack" ⚠ See more info here: https://nextjs.org/docs/messages/invalid-next-config ▲ Next.js 16.0.0-beta.0 (Turbopack)

• Experiments (use with caution): ✓ webpackMemoryOptimizations

Creating an optimized production build ...

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

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

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

Caused by:

• Expected process result to be a module, but it could not be processed

Debug info:

• 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 /favicon.ico/route
• Execution of AppEndpoint::output failed
• Execution of Project::whole_app_module_graphs failed
• Execution of whole_app_module_graph_operation failed
• Execution of *ModuleGraph::from_single_graph failed
• Execution of *SingleModuleGraph::new_with_entries failed
• Execution of Project::get_all_entries failed
• Execution of <AppEndpoint as Endpoint>::entries failed
• Execution of get_app_page_entry failed
• Execution of ProcessResult::module failed
• Expected process result to be a module, but it could not be processed at <unknown> (TurbopackInternalError: Failed to write app endpoint /favicon.ico/route) { type: 'TurbopackInternalError' }

TL;DR

The issue is likely related to the mdxRs option in Next.js 16.0.0-beta.0, and setting it to false might resolve the error.

Guidance

• Verify that the issue is specific to Next.js 16.0.0-beta.0 by testing with a previous version (e.g., 15.*).
• Check the next.config.ts file for any unrecognized keys, such as 'conditions', and remove or fix them according to the Next.js documentation.
• Try setting mdxRs to false in the next.config.ts file to see if it resolves the issue.
• If using remark and rehype plugins, test them separately to ensure they are not contributing to the error.

Example

No specific code example is provided, as the issue seems to be related to configuration options rather than code implementation.

Notes

The issue appears to be specific to the beta version of Next.js 16.0.0, and the provided error messages suggest a problem with the mdxRs option. However, without more information about the project's configuration and code, it's difficult to provide a definitive solution.

Recommendation

Apply a workaround by setting mdxRs to false in the next.config.ts file, as this might resolve the error. This recommendation is based on the fact that the issue only occurs in Next.js 16.0.0-beta.0 and that the mdxRs option is mentioned in the error messages.