▲ Next.js 16.1.6 (Turbopack)

Creating an optimized production build ...

FATAL: An unexpected Turbopack error occurred. A panic log has been written to C:\Users\baseplate-admin\AppData\Local\Temp\next-panic-6cacacc1fe20a1c64325df3dbeddf2fb.log.

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

Build error occurred Error [TurbopackInternalError]: NftJsonAsset: cannot handle filepath url

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 emit failed
• Execution of <NftJsonAsset as Asset>::content failed
• NftJsonAsset: cannot handle filepath url at <unknown> (TurbopackInternalError: NftJsonAsset: cannot handle filepath url) { type: 'TurbopackInternalError', location: undefined }

TL;DR

• The issue can likely be resolved by adjusting the configuration or code related to NftJsonAsset to handle filepath URLs correctly in Turbopack.

Guidance

• Review the code that utilizes NftJsonAsset to ensure it properly handles filepath URLs, potentially by converting them to a format that NftJsonAsset can process.
• Verify that the next configuration does not contain any settings that might be causing NftJsonAsset to fail, such as incorrect paths or asset handling configurations.
• Consider temporarily switching to webpack to build the project (npm run build:webpack) to isolate if the issue is specific to Turbopack.
• Check for any updates or issues related to NftJsonAsset and Turbopack in the Next.js documentation or community forums.

Example

No specific code example can be provided without more details on how NftJsonAsset is being used in the project.

Notes

The exact solution depends on the specific implementation of NftJsonAsset in the project, which is not provided in the issue details. The guidance provided is based on the error message indicating an issue with handling filepath URLs.

Recommendation

• Apply workaround: Adjust the code or configuration related to NftJsonAsset to correctly handle filepath URLs, as the issue seems specific to Turbopack and not a version-related problem with Next.js.