nextjs - 💡(How to fix) Fix Turbopack build fails with symlinked node_modules: "Symlink node_modules is invalid, it points out of the filesystem root" [3 comments, 2 participants]

Build error occurred Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root

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 Project::get_all_endpoints failed
• Execution of Project::get_all_endpoint_groups failed
• Execution of Project::entrypoints failed
• Execution of AppProject::routes failed
• Execution of directory_tree_to_entrypoints_internal failed
• Execution of try_get_next_package failed
• Execution of *ResolveResult::first_source failed
• Execution of resolve failed
• Execution of resolve_internal failed
• Execution of find_package failed
• Symlink node_modules is invalid, it points out of the filesystem root at ignore-listed frames { type: 'TurbopackInternalError', location: undefined } ❌ Build failed. 🧹 Cleaning up workspace... Error: Command failed: next build at genericNodeError (node:internal/errors:985:15) at wrappedFn (node:internal/errors:539:14) at checkExecSyncError (node:child_process:925:11) at execSync (node:child_process:997:15) at build (/Users/innei/git/work/lobe-chat/scripts/electronWorkflow/buildNextApp.mts:88:5) at async <anonymous> (/Users/innei/git/work/lobe-chat/scripts/electronWorkflow/buildNextApp.mts:131:1) { status: 1, signal: null, output: [ null, null, null ], pid: 45856, stdout: null, stderr: null }

TL;DR

The most likely fix is to configure Turbopack to correctly resolve symlinked node_modules directories that point to parent directories.

Guidance

• Verify that the node_modules symlink is correctly pointing to the parent directory and that the directory exists.
• Check the Turbopack configuration to see if there are any options to enable resolving symlinks that point to parent directories.
• Consider using a different build tool or configuration that supports resolving symlinks, such as Webpack.
• Investigate if there are any known issues or limitations with Turbopack and symlinked node_modules directories.

Example

No code example is provided as the issue is related to configuration and build tools.

Notes

The issue seems to be specific to Turbopack and its handling of symlinked node_modules directories. The fact that it worked with Webpack-based Next.js builds suggests that the issue is not with the project setup, but rather with the build tool.

Recommendation

Apply a workaround, such as using a different build tool or configuration that supports resolving symlinks, until the issue is fixed in Turbopack. This is because the current behavior of Turbopack is causing a fatal error and preventing the build from completing.