----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-9b0e5ec97b974886fc3ed7cce432bd65.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-93c82b06339bd3143a827be6025a04c8.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-1c28accf07cb20a8079f94286dd6ed9c.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-8598a1b4c34fb8ec7d268c0d9e366c51.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-8065733cb6eb6602da347ea613277c8d.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-58ce065e71b7556a2dd3f0ee85f75d93.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-fbe0f057efb189eb47f53fb4a2616ed8.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-c1dd477ac87fa2e42c194e963ad2f6e8.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-faaea929d3b5a57b9eb422e4887872ab.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-28dc9c9473880adf152f8d2f4a35d5f4.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-2e7ef5160883bf428b6f57eef7b9a258.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-23186bfec2c15350a0bdcfc4f6abb728.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-7308f18789460169dcbaceb3c4bcb9d0.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-227be99419aa634fcb49155ce0b53929.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-2d775b52f6842c534dd728c01e4e1c9a.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-6892f54169822ebdfda8737929133086.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-bbc6216ad019025336aa07d9d157face.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-43a6dffe01e65f3c614c923c824d0df2.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-7a72162ef199f601511449be32ac10df.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-64053dd56b20feb52e051be142fa3a8f.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-8c80beebb41ab2184335313b13e178d3.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-f76f31f0a653c625481042fa80f29663.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-ff0aaadf2722a3a0ce5b2a4fac6ecd32.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-cdcdad93a82dbd278cc48ba224a9c212.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-cbe4036dffd26d619f86724b978a343c.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-f940a40a9afcbee93a50994364c4b1b.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-a8bf4475df78769cf91431c1fd10f148.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-588f6560c91fd4bb2b9b590854e940c6.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-327be197a862c613c87193aaaa570160.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-33fa6bf8e6fd7296e3a07b75894a554a.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-f3a8eb23854f092892639992ffb0fb52.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-bed19d5fef19f665f1611801f96a57ed.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-4d9924426263bcd4e2528112d0894216.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-d8085a33744eb2091db8f43f565fdf29.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-b2cf47868257af20e37ef0aca3facac2.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-c753361cc17b07562e0b2aa0f8b33123.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-99aaab0c7991e8beea7b82cccb3827d2.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-be20014b53c13ee1c8f05731b7df7380.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-f3a9e6c54c937155a579bcff79793010.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-11e43161b8371fcca8f1c48551f4b6c7.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-bc1d7b26c4846010b73776efa5d4347e.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-e195674d00f9386b5329c3e461b26fdf.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-916595a2b04e602e9fca64f6188da14d.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-8015a13bd9011347a76b3c6964c636cf.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-c924d0cb8060214ddf78ffc24603a926.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-8fdbfc8611fc1396048167ac3719ddaa.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-e049282a7bb512628570c37ffd2aaa1b.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-6df079df3cae10a272d99fd8caefdf96.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-31efaf662bedb8fac8199a536c04673e.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-d1c90abf21e85786665396f377860885.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-9a434a9105f541e7bf4c2a36a522ed98.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-ea9266837cbe3d081b6c2b6110970e4a.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-5c2e33a1234bf3e88d5b8e7928b680d2.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-537b0ee17f7296dd6529b769a7a7df2b.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-86cb0018b1d9aa17f0f99344129b6f20.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-bb82b0cfc9157e6d2fb3c8f1d0d4bb1f.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-dd7456e52da498f495af15b206584fd4.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-7350ef56f0410152af4e4fdc014a9d97.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-421fa49c6c9d722b7c37fe9f18afbd3.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-e8996bf2cba7030ff9df4e8823a4bbff.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-5126f8104a053763602227fc720c2a15.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-fa19590e6b8e9d41a8a1466cef2741cb.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-a88e00ffcea58c91ed973019b67688ca.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-e803ab87dbd374a1f34474b9565dd813.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-9f1b3f8572fff4209e2b3b99d050034a.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-40b106cfd40a2cfc6af4ce851dcae063.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-cf8591835d8eb96f20f25765bf8fd36f.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-401faf6176253f45d7928597aca0eb00.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-32b289f28992c63fb479600f43d1f8b3.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-41bbae9c78faaa059219ae7cb4f1c221.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-a8c3a98fb95ec34bf1f3a28df162d360.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-3623e6269b4ff08833a46a215b7a1307.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-eaee22bdfbb1617bcb192e09eb08fa28.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-a46d3feb4ee75bc7f71862c5bd1ac929.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-b950df80f86f329144073dea155f8173.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-c014a45bd220ced0841561619b772997.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-564fc3994a14bbf4fcac0ae28b84926c.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-825ca48b0a8c111cde252fab5400485d.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-88302b07c75ef578f403e0f1fc6cf81d.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-8c0eb7a2dfe41aae5cb2343a60dc1c5d.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-f8f9bbccf8bdfbb6bf3d5e9493c0ee5.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-bcde55decdbdb90c657f868876c22da5.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-ac3e1eb0a23b64155289c36eca0f9677.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-803969150d56a9eaa02c6dfdf7b38365.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-ccf97b86111d9bd20ca5c3f12771e9e3.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-4ee31568728df29da3fa543d907dceab.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-d09563c0658b1178476ae782b546cc6a.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-82ef074050beec9a68d3759e577fbef.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-1f16b72237d2f2c76de73d8d2312f2bb.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-8546b7d17ec90ddeef6f31565c48001f.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-342a8339926825211ee39cbf13643afb.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-24775ed2f9c7a8ad84d9983d264b8fe0.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-82850c569c22540903c2630841a56f.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-92ff7c2e2ed55e8748dd781183341f05.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-80d2d01993588fdacc986be82eb46836.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-c6d955ee2181e9fbc2311942e4f8cd28.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-228c0bd387c9c5819b85c579d3b8247f.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-c82a3c9bd2f2417825199d37fdb6190f.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-31f607ec4dc4802a6486956961d139ac.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-5348e3b48257807a0fcbc1d1ff249788.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-acd75420d1c24a9fe10080be0bc07986.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-4a05e75514ee1ec8c954a5ca2dca4f69.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-daa3ced3375e0d50c321002a9a9e09e9.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-232c786568a2a853c30d5c1b7f3153e8.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-c4ad7b1c3a915546312d1afa2fa5b491.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-122ab982f412c45ddda5f79a3f6ffd98.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-4fd7ecc6d4e0c169c18f37a3aa9a028e.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-4db4fe505b0c5228235deda133119a7e.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-b1920d1b66e71b4af95798faf988cdb5.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-4a9280e2fe3bac06201469e33fb5595.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-9d5eecb85d95566bad3c521b2990db9e.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-68baa8d50ea42c9406d68a5baf9b80cd.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-d9f91b3a10ee4ca79cd4de77c60d5b39.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-87b595ad59c82e97fb443a31aab5b8d6.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-6fa76b34536489235258f4a71bfc50c6.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-36e0397bb108e87edf640ac56bb0aecb.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-1e6c7608b6353a65a26c6b969290c7c.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-8de26edaaa16ba0020ea39670b1d911c.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-9fd644aedb75eb0a385aa07e1c771548.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-71774040767aa1e2a02356b0d6160fe1.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-37bb39f68653e796df7be626f4261d9.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-cc85e54c93109aa8c8bf941ae08bf7a5.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-9f5739f3e953a40a88b5dc688dd1480c.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-7fac0dfa7a7f2e03b97cf2886ba417d1.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-e095676563df17c49409864be423a9f2.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-e430da981c143ecb635c49df3c447178.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-dab74947d767b7f2f04f9991de135f8e.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-de4686e4852b16fc027b3ef234316158.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-218cc6b8ac8af1ab0248c33ea691aa81.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-11b233f6be1b74d780cd2e13efbca8fb.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-7aea142ebe25019f2c4d292f442e57e8.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-66beadadcf20dea381d389ff7dc2aabf.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-dbf245a1fbf95baeb45c29fb34146ba2.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-cb4eebace78fb2320d37832f9ce4e408.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-3e14a355f818c1410f937eab53f041bc.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-d80bfa6554a778978065b6257c627a84.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-d78046aced1c0b51736bab511703c309.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-b1ac701b1e6a240927b9d577dbfb5aec.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-72c35f1e02d95d73e2ece4f5d4544318.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-7c7b8c684cfb9fff402745705f32e2b6.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-7c156114c7aae0bfbdbe2818afd8283f.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-bc11f31a8b1ba4a61be67c71af0a0d25.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-48a258164baeb40bc4d96f9556474697.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-8a447ff16c4c5e2405df6ede8d85b114.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-64be44e79f17ad01a56f095c7774001d.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-9c771c9db706ec92df64373374b3b5e0.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-55bb36bab6dbd18804f224caaad93545.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-9f1b93684ce1d442084c5c9e93e513f1.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-1c92c3e044daca6380dc3c8937c9492c.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-182ddd53d2b785472b6d219e6b9a7182.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-281dc748e4590fe66673b9d87638beef.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-32b5d4b073daacc208431efba1fe4a01.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-755004fb4f6a286df0b55484e02ef946.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-1357341a90ce2c55086eed64be04cbd3.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-d8090dbf43dbfd64c846e41dd909df95.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-c33cad0b6f301028187bb0636ef0e69a.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-6edb2c90dab29c2faad5d8815ecd959e.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-cfad398d57bf9a3ba471e17c37123c2e.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-6068de1751bc941b64d85f6b24c6a837.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-f33443185c603a235c68dd8a1dca719a.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-541956b3092d404f8284c465e4fd7eb4.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-aa9342f7014126e9ea524fdd96a72c26.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-f5fd24b0b782e29d995fb51988582945.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-90525392afbd4f01ecfae83842e0db59.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-5129948423722131eee48ec4da24551.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-a6ef9614317bd8f0735af2faf58692fa.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-326625162ea52c2a686ad07c1a629d92.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-9ade4ba2e6f497c141786ea1dc7378a.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-bbc16de3a04b8b29448ed707ffc26ff2.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-d7bf860b1153616fa4b9f31f2de7cd9e.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-b8d204466957f37b3f1f116a09ad1f7c.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-d758d616ebe46eb12710da4de8aad6a6.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-fb908aa4268a6be47fc5e0f34b3bfd43.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-7941a755b6be915b70fc6aef77fa3bef.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-5b473920bc24089a26990317c16cd170.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-397f32e822dead46626ea57a4e3f29df.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-113c5c27202519b3d5f7ff0ddcc6b99f.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-f5066fc75b6fbb443d765650e8ed6806.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-fbc3fcf0f2a747520408da9126ec1b7b.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-f50bcb467a3447072ffe93cc6aa0da00.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-e0331808d3c9f0146eb4f12175cfeddb.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-2860906eaf5ab2a2ece975665e953b1b.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-2999dd12b1786f5ddb76a7554554445f.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-113d1da84f3e8e6aeeebb58984a1dbb7.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-80fd94e2ed747df7a337e38423aeaf94.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-bc835aca02903d6c994be70ffaad91c4.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-51ec9800f8e25b31c625fda4dcd0673.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-59ed5b9ccea30082bc4229d2a0fa82c1.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-6615d7212f641dfdcdffb6d88f493cf2.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-96356e8d864cd04256aef2acd5e5ecb2.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-dd5a24066e57d178db054a19233b6046.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-c5bc6f3f2e39dd094890e37b97a054b5.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-edbb3420da73a1a21753edab8e30a461.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-11b77c795667cdd99cdb246cf189dfc4.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-87a5a7102fe4ebd641da4dc8380e45d1.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-49c5180e01a7fdc89810047a86efa96e.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-cfd288d1ae40c2e3e81bbd51754fd834.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-2c0fb56bc6496555b2ba073bce6fd53c.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-caba4317b00c1dc0e5526f47e24fcc92.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-de1da09f911795a5cddf1267c0a2174e.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-4452127d5e26946577314029ba981041.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-f16410b33058a1a096980d2599130059.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-4987d8932ee4e50d5040bb1215952fd7.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-19ecd83b9e53ff1ee44cbf3f5812c7ff.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-2fe42ba08511857f28195d58af175fc9.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-8d9b1fc719713e310320303fd2eaeb0d.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-a73e70cd2d393e26b8f9cf21b92c97a1.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-ae655078ffdbda5ce77028cc62defff7.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-1d2125bbebe48527726af6fb66687885.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-b7e24dbb618139808df0fd3302ac6283.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-3300c6335f1501e25a9d4c4d7fe397d1.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-87a748ae528ed5a5b6cc441457ae390e.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-4512246f8a1d76bfca12f01bcf05fa67.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-c8dafedc04db594f887d8c52ad893404.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-af81a0052f30f50b54876137a2bb9de6.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-e1e97b43cb8ecddd66fde24f45de0496.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-a85ced37dff88ea15be261b0b2b9cc55.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-3cf6c547e28d1118413da98bf41b400.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-fa31c0c713fb8fdf32dcd9dea019fcbb.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-66e53dbed6a270147541160d122eef00.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-f0f595527edc4400b09f6c24583a7e9a.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-77f86fc72b38c54a9688b35801f08fd.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-7edb63c0752e3fd9211998589b91615d.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-7c1313ba7f21e710c856e063eafff286.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-8a185f88e85f8764139bfd0b87918256.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-2c1c61e9b089126e895469a8f290edc5.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-4b5323d22cf5e6fa1aac847c1e4f7138.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-efbe4242dc5b62d32ff0a7693ee9e399.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-80b9a667a1693df99eb269f205f17f01.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-e85ede8501347f515659e5db4d2f0db0.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-678d2948d3a20c31d3fb9bc3af1f621d.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-855725b6ebbc9e5b32ab67d84e436079.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-397a1a5d07714e383ed8355504c3a915.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-af7e5fc8b8e487b163e912c012d40536.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-13555d3b4e237447fe6f8f2d4d358b91.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-982fb34a33411211dc06410ec3394a39.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-bef12d58332ea578a94da815ae1b2dc3.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-727b626b987252b6e38087f127475855.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-8b885914a6f9cd133d0ff300fe4ae36e.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-4ea59894bd99261f5efa7b838843ff0d.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-8ec3bb722d45eb916f4e6f300267fbd4.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-21b3ac14dc858284f6c3fcb199820099.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-d5da4b1a6773962de14948bdc825ab00.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-a12bcb651ff9162e376c701e319ec3b9.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-81aad3b2821ab5e163d4957791238f4a.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-1553aebb5ac43a834684ab433b421d7d.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-aa560c24ae0afa4ab7bde87281dbf497.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-626c5404eac23b89b36fbeb52b60c274.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-e9561a424b42fd8aeab92b570035921a.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-7c5962612cfb86d4f01db14f654f58c4.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-caa161db86005b6c8d9b440a87bb9e56.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-f96897994d5d9ed21fd31742cc82359b.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-faf86170c3f071e96e79eb2a897b7b71.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-fe93b90d8fff2b37297167446f0f3cb6.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-eba8136fa21d23533f11687253f061ed.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-651b3801ce7cff7381d99a3e164e5cee.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-1cba3fa21500e9a87137eacb8268edd4.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-5b63c27da2238bfd375c66fec554391e.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-52c212b4a5c1f41008d1e0360ffe6825.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-b70668dc99f214eed0ab0530f29bd563.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-f97fd37d20b173ac91046bdce917bf26.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-b2baf7cf7bff35f5cc7af87a722777f3.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-18b67094b0ab11c3180b3fe3eb2bacb2.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-bd17a748f3a95328736fced9e830296d.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-4477d4bce0140150ab9fb470e04ca37b.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-4740acdb3b5de1243d8c2e457585730a.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-ee12238df899fcbe12680b8eab4db056.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-dd8af7ca87b23ae689305789f6982a53.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-12beb98bfe0fd83be6702115519f537b.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-f5898cff5fcf259ed7f9abada6d29560.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-796f7f7029c758683e34183ce1c9f081.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-d6538fff8ac24b04b09db92d7b753fdb.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-c395f90902dcce426a67992b0d5bb6e9.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-ab0edb78251f7b13d70c98795dde91c1.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-3c6d6d0ce2059632f489bb646ca03bee.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-b39a7f60392f1c90cdfc4549474444ee.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-b753947b557ab72ffca295ec85e02693.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-456f18c31274ad873221a0f0595f1fa1.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-97fcc8bec0d505db6afb0b86d80613da.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-90b11c622f9028d2981469ae1c3e9801.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-2a36873c1a3fb3f3f00a80113cc822a2.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-9f0d5b6e9fa09514ccb02402999b86e6.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-f1371c9947b46d46939e35114e5ef8ae.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-3035d9d04773b128a778c769d0fb370.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-5e389de99a2eceaec4d6f5be099ed117.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-61069e4a45066b7b1d42bbfdea07d450.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-fd1584c284456b0cab4d0aa710fc66bf.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-761ebed81ebbb67ecf7d376eb5c123fa.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-4374274f46504d2163e9a9f0ebd521ff.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-40e7194e8f80e304a490bceae181701e.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-3b71667a98fe0d733a2d2a1491bd78df.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-8dec747da67b3ed103126564220172d4.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-fbc9efad3855284b0e5dec8446e15878.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-89fc0868b3e393872f6c99f0fa7b80ed.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-7056646b87ebc2146b7f2d000f054487.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-4b8b4e01d23f252abb3189ae148933dd.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-3be08d48de0c213ad76d0b43dc4fc12b.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-faafccc0424b5da6fcf2a0471344cbb3.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-9511c8b17b7800941e47948756cfecee.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-d5ab75a7d47bda0add633a523182e76b.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-d431740bc557077cd156c904bce10d11.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-8372520610bb8ca66b96eea163d27888.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-f3e52ff2e144e2450cb24981dccd280f.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-3eb761f94833748b6b3c781d5b9abaa2.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-76e2b3eec01a3a3dd73fd295716ce0a9.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-7bace376589f5b9ef2d2cb5fe1a058e6.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-3d39b87aef3c0df0b784283ce61f9c2c.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-82941d5a7adbc31136a5ac67546a1621.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-8aab4000132ade4451eae429a478d268.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-b6e4e630c933a6a4294d0ed2a5129d2d.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-e357f188e5dcfb1da390d747b1bb7914.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-5685110ef2e2796afa377b5fc278087e.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-1d6de36a20c927141193b6d9c5984307.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-a52c4c3eb788adf4c0a480081f6851ec.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-d24b1ebe0bf813a043cba8b83e655006.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-865ac4b2da442db0ccc0442c4744208d.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-274bc7eca128e5e10338d9fe31de7185.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-f7cb5f681434115303fa953646b37bac.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-181c7cab5de5cd36fde5167b8016dec1.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-4ec0f142399295f732aa89030ef91e4a.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-cbb6f93a428535831f7c9694770a43c4.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-2013f44409ea684e459f0db3099d67a.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-ec884a352a1f1439442f46f58cef1674.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-6cc05b9493f05fc11538d81ca4520a1e.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-77c8e35b6fed168a37985a0a7f72ff05.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-e47533e72d25cf6a4b5fc45c4725c0da.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-492614858638da177cd9f7dea9b1b813.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-9c725e432d7da309c3ef95844e4b24be.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-e93919e8ef83cb11d3f5e50b4fb757b7.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-54c763fe25aea85dceef63e8703e0041.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-fdde9687b5c21f4715a17ce2082d46ab.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-e55cb2de06cdc9e63b7511189504ee9f.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-596679e872833fd5de0542d260631fe1.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-b766e6c4a82e61769ba93919e65b22eb.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-c51ccc2cdc29b3592ed10823d0883694.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-cbb59ab85382047a3f9ed39fe70223e5.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-e7c0045955abff8853c143f82cda13a6.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-fd80835d1f98b9b84c5592eaece73298.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-6fb74035bce1f3c5c07ee6c78ffe6800.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-34021fef18760724e680d3ef44ac39c1.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-fba060726f6e5e23a8e249a02946082c.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-4eb45827567370f9677ee9ff7a0accb0.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-b0cbfb1dd312bb9715266165edb94536.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-db614c19bc2625619e4805a56f5941d4.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-c4368da87cb1430468f5d47ec5af8bc6.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-da3f06241013fe5901a9f138d24a15f6.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-1b70e9a031acce6fd03640430e70f8a1.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-ac8e73607ba81abd7d3d229524d28537.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-a1fa0c05406a1b0fc3a448540af5f0f0.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-a667bfdff60e5f07f111ce9d0cbdfc7a.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-740c52a2bf9b1e96b72405260cbff00d.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-60cdf61a14bf1e0bb26eb550c91d4878.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-d73a276eb4068859d8cca9a0a5877a40.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-8bad95bbc86ab37ad6f895fa1e43c8c3.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-8570313290c2ffa224ed4f76ed0aa522.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-2be6c1ef96b707c7df418c715912fb6d.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-96c848672b000881573cad249e25820e.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-b746c383e6b514a4593815bce25e7a42.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-77491e5c6c292a0d8343f74287488a54.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-8df7276d6703656e31d46f8462d8d97b.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-720ff91c9945d6bff963eae0b9047cba.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-14daeec4c3e0e187e2bd9a2a450a8c4a.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-b2ddb4bb20940b23aa61672906605d7b.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-4b7f66a376835c70bd89b3c2e7ba6cfe.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-bf006694ff4a1ee6e83384b6ca8a4764.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-e7e01ed48c43337a9a27c0e9305cb319.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-f5026e90c35d82e5e23a012c778887c6.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-44518155e6b10590a7d7d6dee3f51b55.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-a1c64477facb9e38389826454190005f.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-3a2caaf6266446d94abcc18a40742505.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-1ac42ad7cfced448b10c2e4a24a3bc2b.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-8b4da0db973aa1aa962b7635fafb9192.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-1fcf9a9127378273b2beaafd57c77977.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } Exception ignored in: <_io.TextIOWrapper name='' mode='w' encoding='utf-8'> BrokenPipeError: [Errno 32] Broken pipe ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-915c3232dc59b869b96bc7f4fecc3030.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-9c329f39a38cf5e7273c00563c29ca57.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-2ee658a3ff0c9cc410f1474c77136f32.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-91f5460550d6edb908d0f7b2be5b7de8.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-59fe302bf46676c0958a4f4fbdb12504.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-557b6a6c3231090ab44a26ae25a834a3.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-572dbda49ee771b9b3789b7cd5eb2bba.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-f24357b00225ee3a5256088e41a8d5f2.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-770e843ecf5f80d113ce0161027c99b6.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-365d694872582dc38e8e44826d203a21.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-90a06c9df6eebbf293af4b06bbe1c366.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-7c1884ac6d14e70a9df378b675b81108.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-c4a7254da5686b1e5dff09f79aedc27f.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-9e76580fb8b29e6b3b6ba88787e0feb3.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-4d71cfd4b5826f364a00f6d8f35d883c.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-cb7a832d1b999490ca33db437a1a2553.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-c4167d18d5d0490b4381e3e71c4abed8.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-6d00368b2a26e4aff1d4877440c5647f.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-42d597339efd8b70b5a9685d2f8be8e9.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-9fd86f4b3b2e326730e382642c05af64.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-191b39f4ceace7dbe742fdab784a10c1.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-9051614a3f9fd929cb93d8ebd3383802.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-fe6bb171f493905f6526f61cca050949.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-9692aec2ff697898e6fa80cb82146ba9.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-ba43cc52a75cdf0823c4a64b3fd2336e.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-5b626f994f13118acacc106e5cbf17fd.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-ebb7784035eac689dbea81a1f2ae6f5c.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-516c59cf1702c434fc14ed2862224069.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-e4eed05fb8e5274b1c0287cfe2455f50.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-b5edef1c6502b734ba2b23c226b00866.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-82e88f5539d39a1b0939008d9f07a44e.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-ca3ac57d9435dc75fcda62cca1f9aebf.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-6a576dda0a8010359cc241bad658bc9b.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-1dd39af147d7629784b59572b1e19a5a.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-16dd1b93ff0aa99278c8561c8d5c371f.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-fe119b5c878363f48c2fd318a965d2c2.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-719ba4de8420bccf7be2410522392fc6.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-c11892824eaefa8f4ebd465bf019e15c.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-8630ed03ffaf713418286e856ae714b9.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-5a24a6fc630b96784ae87b4559e01571.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-4d51617d15f104941e45c4d8a9f8538d.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-fa62ff5294c3d416abaec4526df1e37f.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-9675c237c994c5b0482240afde995ddf.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-c583fc91beb0fc201263fa3d665f96e6.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-a125a33ad2237c3f03b5cddbb52dda7e.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-fa36c446b8d2156c028c22df4c2db156.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-b2959fee01da94fa228fe40b69202ec5.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-5791b0a3725c0a33631e4160c750ec93.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-8c99de429004221404521bc331333e5c.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-3b37a89952c7431ed1548f99b12748d4.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-434d2c122539028c4027ab6015dc2592.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-6cb08b10c63d513aff98cafcb06cbbee.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-b962f235fa20f3dd712752b98889bd6a.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-6771851142891708119901a381db2875.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-b3c8ee8d522c6524e39b1506d8718519.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-6027880deccfa1b5fefa3ca7c23a28f6.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-6f2105af567e8e5c017f6c72e61e52b.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-4a5968485fa3328f1601a4058fd3ca24.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-3224ea0ace5e8a4963ad2704e8e11842.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-4cf9ce12c4dcd0e03d2515b87c851548.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-eabe6d8974313ef2741e697ebece7da4.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-aa14b0428ede61cb60a0786cee0928f6.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-7dbb974e6d3e1d45a24adc475c242a88.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-b617100cce92880bed519957f35a57f6.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-f04cebe3ee21031b7acfaf093fa35d3a.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-606c46a17609c708bb93ead17db51574.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-70f650de1375e04f029b0ce22d55044b.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-4dd6357b97119e72202b4b75a3cec42c.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-17497a9ec82da66b70d6f0c9b2648a18.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-e7d47a62c87475b1ec8018518f458a95.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-5a504ceb6b65ff8495b20e048469b343.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-d08bc2885b1c47cab59bb95e542a444d.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-2b5a673a2df6c9c461606c9dc93aa7c0.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-6e9d4790d25981cc4ccffcdebdf1b702.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-f0cac7fe489408fdb3b12b623af17797.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-bd49e6d9fa7faa02a1302641b41665b4.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-8c6cbab70d9a00778dde1efd44e51943.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-ea252c2673e23c27d7cac762f70fb9f5.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-3f21de6961e1149dd023ed6fab797604.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ----- FATAL: An unexpected Turbopack error occurred. A panic log has been written to /tmp/next-panic-da2a12441010608c0e0a405e9e6bc81.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%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root&body=Turbopack%20version%3A%20%608227f85d%60%0ANext.js%20version%3A%20%600.0.0%60%0A%0AError%20message%3A%0A%60%60%60%0ATurbopack%20Error%3A%20Symlink%20node_modules%20is%20invalid%2C%20it%20points%20out%20of%20the%20filesystem%20root%0A%60%60%60&labels=Turbopack,Turbopack%20Panic%20Backtrace ----- Error [TurbopackInternalError]: Symlink node_modules is invalid, it points out of the filesystem root Debug info: - Execution of get_entrypoints_with_issues_operation failed - Execution of EntrypointsOperation::new failed - Execution of Project::entrypoints failed - Execution of AppProject::routes failed - Execution of directory_tree_to_entrypoints_internal failed - Execution of directory_tree_to_loader_tree 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 { location: undefined } ⚠ "next start" does not work with "output: standalone" configuration. Use "node .next/standalone/server.js" instead. ⚠ "next start" does not work with "output: standalone" configuration. Use "node .next/standalone/server.js" instead. ⚠ "next start" does not work with "output: standalone" configuration. Use "node .next/standalone/server.js" instead. ⚠ "next start" does not work with "output: standalone" configuration. Use "node .next/standalone/server.js" instead. ⚠ "next start" does not work with "output: standalone" configuration. Use "node .next/standalone/server.js" instead. ⚠ "next start" does not work with "output: standalone" configuration. Use "node .next/standalone/server.js" instead. ⚠ "next start" does not work with "output: standalone" configuration. Use "node .next/standalone/server.js" instead. Error: Failed to find Server Action "x". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "x". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "x". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "x". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "x". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "x". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames ⚠ "next start" does not work with "output: standalone" configuration. Use "node .next/standalone/server.js" instead. ⚠ "next start" does not work with "output: standalone" configuration. Use "node .next/standalone/server.js" instead. Error: Failed to find Server Action "7792df89195b264a3b3a65ff288885ff4d8868e7". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "bf7e75c55d01d51dfdac5fa9f97c4140775f8740". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "e1801eaeca1b61ae1e10e2caa130a6d998643ce0". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "6bd6479b1059792999d480ceb6a129a916065e93". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "8fccc2c27bbd0a68243d64c28de5af5f776c3d1b". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "04daeb7cef7a5784aa8d546293ca1631225e090f". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "3a930cc8bcc886849980bf490332b9b91e5ca0db". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "c91295d25ed3d19ca65cdf4d60bc42b9b38d3813". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "6f06b3ece9ee3e33b40c69e53d4957a617f7f285". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "38a9cf9d2b64efc3b68dbfeb603f92238c4dc2da". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "4002d688ac5c4885963826c0727b2d12241fef9a". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "48b3380f962a0834ca7319304920e76858cab205". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "8877b74220026eba43acb78596b4e84fdf32a7cb". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "b0c42f439abf952ed08d9090c92ae8dfde1791e6". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "bd52dd007d2a743fcf070964d2e59d57a5749534". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "9896801ff478973312b6bc4af8c062f2db7afc7a". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "dbc5bd5b33ae60f8f1e3f224333346e7d15569fd". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "2a823f2fc8e2db696ffd509c0228a45893d5f810". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "3d6d693450590300e1af268578e4a23352d8baa7". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "342c48a5f7faa6fa00e5c8578d77e1ca445ac1c0". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "ffcfd9f3bfb3653e932ccaa5fad8c625067e9505". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "f855d3784f68ad9be82a27ea7b59e8ffadcc054d". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "fb53de3523dd3d0f349d06beea584e3006f7511b". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "1d18972c9011bcc9cb5ad749d5937298f49651a2". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "4f591936dd41bb4e59f033b4da8ae1c76fd46c45". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "4176e93803f0675c3142aaf06fe819ebf8d2b2e2". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "5c741348c0df5d211f6b0b9037164bba891b592e". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "cf03c8658e3dd75e297fc1f6d86f59f3f518f642". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "d6b03daf2af44051a3e3b35e457a6650746b8eea". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "3363c7b630058c5f1320e95a4df6e662067806d9". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "39a2af1463ae9378f2d93c32873dc2c8d8297165". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "ca97995ffbbdce149ffc78f67ce8ce1417c21506". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "6e258f7fc9b3ced6b632404571395584c3436fc9". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "f91e2ea45f33060d5b8199481d5d654779290d42". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "6942c5eca5d78b8c52446ee7ff82f841ce4f31a0". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "66a470ce083244df3b9da13d75a2185f1495a6f6". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "1928f357200f1568035412533f64db4a00d13039". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "738a3d9c0d88669c2aaf2bfc5c11d242757f8839". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "512ce576e46faa80811ddd9072cbb86efdc635f6". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "9ce5c8d2fe11178f286e99085882bedce658a602". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "599f4e12dea660110d1b931a21636bcfc7857998". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "3722c97a5ded9b2f53d7b3f7b8034e066bdfab65". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "d03c049a30a27c85a39cf0ea16d666f3258577a9". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "59a86c92ca5751f023602a6af01375aa793288ff". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "95951f92ae8fd58a0d36f254bc53ceeb86e41487". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "d9785a8389f8d3d1fc3c196a345039dd3808d20f". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "17b23d60630b10436a9ff496dfa2d14623261e91". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "911f40f0e2caeb21f41abe7392591bbc0f74acc2". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "76b6a1027a9d9e6a2048f8a6bc31b06fa27540c0". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "fd619f39160d47c4755cf5a691eb42adea11e192". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "34d36d7c1684309dd31a1d54f4bfa7e85a02b3cd". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "e0115ae2dd6689b9c830dbcdd73f0403b2d1b3b6". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "c85183ccc962757b5c1ddf4fcb8ed415348c47c7". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "0cd8981fc8c0b83cd47d0579d315fcddfd9dc8ce". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "51bde2908f714f249ba364ff0680745edd0e7a56". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "d40f6c91c55724c3ef1121e7f7138166bcd15cb0". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "e16d7403cce70ecf1c2ddcb753139e739c8aab72". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "5c1a35b27742f32f359efa52013d67909b8ee995". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "30992d5b9b48b4bdf4261da00d7eddfa914896fa". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "3bc423d91b7506ced67bca6f8109fe60b02068cf". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "18e61249f45b4c445a4f54e060c094f1b088fb91". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "ce2db152570fde17796875c88b259ce4b374a84f". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "84ff3b4a9b90c5a04b009aff92a04b9afea50c84". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "5d98205bd4367bc9accfcf9c95bd5f1f1c11751a". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "6224a26f729e22128023e9efb295fc3230719c5d". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "323af3831ac88d6d20029edc430c63c15bc63fb9". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "61a7b1f190c0cb0f358d7a5d9d866e98e240e211". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "c31efe9c3f6bf721694ac51571aeffd637debaed". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "fc6b71aa06943d60a2570b9b00ce7d1adb923b82". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "a83bc3bb000c766cbca360cc93c5c16535e58ad3". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "dd4b11bfe9567064be79b5e521fc6ae44243f1f0". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "d3addfbd5e6aa246cb4e39483bd6788ea5bfd29c". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "043a5e43d60f5997a02b1d1e87e55236f95e5655". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "794b73da81079c5fc5c27558a7f6ff3d475e67f3". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "de8ba1c46e158dd6014275cd76dfe9c3c349811f". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "4563691c4660d0ef1ac2f4f83176b068fdb90224". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "a1f781ead9678747aefa3345b6aac3941d6b2222". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "a9bfbf170f082dcea0f03ea5e1ad7534da3f5962". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "09afd2af95eec3b185a4385ad0fa303be6b927fd". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "f39625fc5bbb36f4beadddf72a606367e900b7b0". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "da066cbfdec317668e58bfa51e0eb98044448ec7". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "a74786ce434593bf964a51922958dbe57ae09a24". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "31f60f0cdf2a8ac39946fba90e28345712097ee8". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "1dbb982efb20274b648436dacc49fa9ef69c784f". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "6b607c14ad8e7edfa80d999d8a9bff95490e68cd". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "a3d38483565777c13267c5b6206345538f10468a". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "c5d185d8a84133f53117af26451f402306979ad9". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "ceb552f2e3d98f439cff7b0aab1d18ce71b56ee8". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "589e7e61321ddb65f9482c22274ffca60c0e5117". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "8bec9aa7a465b1c09f2327a58bdf877ef6f41cc8". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "a7bbd17f40d42bdde54a1bfa36fc04d3417fc02a". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "7442c37be65ddefabf814adf6757a68578b83486". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "575f1b2c4a09445d8324d813931f17990971d261". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "3cabedd8e3c29caf470506226398b346526b1db6". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "f93fa9dbff61f6b3bd4bc981f6a0f8242367735c". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "fbf31c0dc15a8efa54188fdcf99a8f7e1c9c318f". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "a0564e4de31ac2e81aaa2fcbecba9908094f3353". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "d480e5005ac11fecaf2854532aa42f7fd19e5e68". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "3889e6143edb338b21e4307800d8bb6d59dea895". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "5793aef3cd9595fb924f201e4ac5da904e5675ee". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "cdf509f7ae69c8b2494236d300d6f5fc16d407bd". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "fc2b333d70ac7133ed8858d9bdcb636bbc0348a4". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "0ad7cb5fe06142888a6d2cb028b8934f53ec9f6c". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "202d39fc51312c2158cedd38caf2961f13ee93f6". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "592913a0dd68397546af766a02e62220fee44e63". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "92738777ca1dd9b580f1d84398edefdbeec352a6". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "ca4fcf79e504b28cc129fbfa658ee5bdf54071a7". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "f1611eb2480f97307fa3dc6e58d38b16b4b1b210". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "a7cbf4d768bdf0d99586100b3f835e8bd48f52bb". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "13f55289fc3c713a86aef8cea05b3e10313f6687". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "6a892e6536b1d94d4f3e9829a9b6db16619b888c". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "ab00e1643212ad748d870b463fc362bdc4997c22". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "292e77d88cbc9a03302a4dc49fb22360697c42fd". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "a3a2666d98c3d8838ec2e2f2c9599254c32059c5". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "9e6d830a674f8bc04eb6a6b0ed02cb7ae9113946". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "79bb3788988ff1372a9cb7ff1ed9f9567b2b1bd5". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "835acfae9fe96dbccfe5c0c1ca4dd17b3fc65926". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "68077c27754275e2ce35dbb6d8409658f14ce959". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "c64870752e15835ba2ccf9664dcac34d4fb53608". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "6da1a5e0151d07367c521b9e0e87067404bab489". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "d5633d38d940d52048eb03e1b52531689b54d677". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "4738db323b27dfb0a7495e328694518a0009d8bd". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "29c03a4eda872ef9117d3208d1ad6b2a64e9104f". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "d34886187f1960e3d30a7130c8e3c9dc3f666466". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "a704709a4ba1c41fefa6e10b8a6c657f97e78dce". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "08a35f4ad0be2f0c5d4ce69e875221fb1f9767cb". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "8947f1f54fbae12209e156d2d4c9a14bf22b988b". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "40b46885b8e14bc84cd68dc49ca83c219f972619". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "087173596a9571d858d2d7fad573e4152d031d73". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "28909049c4febc706abfdfb98cf244a47c16974b". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "c935a9069376a7f1e59cc6228629df8eb06d28a2". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "6a634786f26fe48167f12ee5c1670eee1c70ace8". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "d6bad72fe26a092b8cf6be2357658bc4bc83c20c". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "3f9753d976b3ba9ba6844e24b0ba49f4d7b9519d". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "2175098aa32b8e3038fcb0ef4e288de665c5eda7". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "b0b3272a3417c14daa5e689fc5cf9725142e6632". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "a02062f2ad470ca641ef551806013e7a3025ef6c". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "f0ddb0d28386c2812edde6c86a536639b8360575". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "fff7116709659bf972d3642e62324711fbceec06". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "f3c44aeed7958fe57100b8675efe6081f0da1f93". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "32cbe68d289e3b100898cd69c7821530bce1054d". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "eb1192ab110ceeb0720bdee6cafc500e87d215a0". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "bbc01b10a913a15cc40691dd19e8f00311c98cb3". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "d0ee90bb334080b315e73d1100358e2be6e56129". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "0834d09c6accf1a1cff2b6e684edbb3615cee4df". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "486f52b82b6f0c85930fde77cb865290c58c4d28". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "50d0a7b2e40df5c0e7cbba004515210adef6d482". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "b9b4adcde9be061d6170c984a74a30661c3e3fc8". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "ecbee311c8b3da3efa312648a3a47e6cf409f033". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "67c0ccf035dfadf3d89a2bff633e810b38f7a1a4". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "564b91e4650109f22ce7440f4f2cc12fda3d353a". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "a5886426c461da4e3cc95f5bf3509afe94c38217". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "8d958867dab8d11fd65367d79dfb9da7ca0eb0f0". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "ec2bd5617d98d5dd0c42723ef3b7b042985318de". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "aa056a687503a3087cbd16453b56d19302f95952". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "297ac5944fc558764250b560ca4b0b6f75385b84". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "c92187471f678032c3bbbc53f07820c5a37e3115". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "b2197317ba8cf2e9d1b9c1f5cfe6e82ed2c0a414". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "49459af78365cdfd202ec739b6372bdf23bd1ce8". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "4d6459ec9257b2d80e93d14d87f1bd782413695b". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "72f4adccbcfe88103073a04b68093eb505bc46eb". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "0f1e910bc345c56616d56b10871edf705c5153ae". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "c795477c45d7a8544a49b911bfd1bebde92da1cb". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "a88ba2639c232ad3c5e09f788d15177fcbaadcd6". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "ba648ea8d0da67d64aaef29a899651288cefe7de". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "58fec9c3cf20a9a2acc643c7c2165105cc980a8b". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "84766fa78d5b53361a65bcf00678908e4b83734d". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "37b0c986cfa09024bdf33beb1809622484f09a01". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "7c62abc45ca152bc530a8b67471c0ec5805ad22a". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "2136e3f6ca510aeae7df1d752024db1086940961". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "51d2a03fb08c8c3ceb1612ff4ab759edeca9eeee". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "28af73528a8d9c68ec1180cb5965de9da41013ed". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "1304a03d7e6b77e6b206dc3ccb8005d6916da16e". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "29740858736520cf64c106f9626ce2781fc3bf7d". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "e43fad040b4749124a2fbfd457cbf6f7ba9a05a7". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "1bb01d76b5bedea6d139c8072648f3e82fc06fb1". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "3d6547c2ebee1ac320db1a51dd50fb878eb47e54". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "526feda0e4d0d2d68fd71bb0df2deb8f39647f44". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "8c8b683208aac12eaed76c7e54ba1ceb1cb79d92". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "b2e3729f07eaa9a074512bbf0edf800f101079b9". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "59a80a98bcb1bbc51b3d32f7027616c757bdf638". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "8f112d90b57d47f8fd95af4d1cda0a2fdffbecbe". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "aa21ce203930f388a9f7aae94ca6fb5588ab8de1". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "1feedf5f04a787755f09f43662bf6cd0d5b062b6". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "445672a50690bf8237aa0f821ea211e8c12abc8b". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "7b3dea42d95879afcbe45266a30114036dc241c8". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "0e6dcf023d44fa0661d8eb99611cd5ca3e9d88db". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "3cdf6d03e63c8ebc1b5bc57a6374c7513e76bf3d". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "709961e7a080350f093e14ccd54a67552cfb5368". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "943aaaac674a08c72e14b8754a91b7b1c0b3d037". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "8b7789cbadcbfc17f5763e36d58f4c542027a762". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "e73c05993398563797c5b81ad24bcd8c7dcb68e1". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "d8bba7ce811626dee1d7324ed2a55efd8f116d58". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "70a7e44f6b1c0c4491473e668518931134dbea1a". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "da9832abef05bb4b188be8cc81e995396da705a4". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "cf37a34c1064a5271b03a6a63e9b16a2d100f679". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "ddcf0fb5a2e9caf381e9ed213f1fbe731e555179". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "6e2e228055e5180b1e3372316c8743ab1a5bc92c". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "d788019a74933181bf9f68ded0169643a8842ce9". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "8c7a912ba6bc17bbd624693fc4fe6f796a0874f9". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "77fa31946ee96dc86081bcf1c2e73e3be4b24c77". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "3ddd154d4be90ae2a8d6f5f4158f67e6362bd3fc". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "5923d3b325cf6fcce4e4bd22972938c297d7e5b6". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "1c8ffdb3f490c076ac5996f4bd46cdea5dfa4601". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "220da006defcd66d9396cfc7466f371f22894a9a". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "f64f2528a7d5b356f2d37e09e18f5e24f86bf3d7". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "3df80373282bfed1388a836122954b928677f7e7". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "5efa6691c70718cc03252040df4ca99e4c7c116c". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "ee0426db8b1001f2bd37c1b99b9bb462809c0853". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "cd2893de36d5a25641b9522d9b1eab5511ef891a". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "2712091dc14508cbb94eba9b7163879819d60af7". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "cd5634f95dd5c8e361367a3a85046969c31eabc4". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "9509a503ce7b484a70a7edfb457d6db03894859f". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "1233cf9a18425c3930e393c819a9648619c1bc7d". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "018f70668338eb4cc4d8675f5ba10e07c81ed220". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "36a391af2a22f3fd7b011bc2c3e491d608aa9a16". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "387fd64bed6bf0a1968f19d56bd7019d04908f3c". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "ea95d19b169ade3408a203406dfae0f54fbea535". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "171ff149147871dc3c2863ba60e942917f9e6612". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "db42a5f5913d3d8090ac4032beba90322819fb9b". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "a69e29f243b0e3d53310123f442553bb4f970387". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "97bae776c5e4ff16611284d355c10e9e222fb402". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "99a4bd2e47e666d8343ac41c28cfdb8324c87ccd". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "0cc748a5f4de18033d6dd17d3c01c99122f8724e". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "b56e7e9f324bb24c620c6b2ddd50c2a20931ba03". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "dd9e1778e449c2deb163822e0bca72142dac3860". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "22ba9a5797555a1860d7ed22e9f6abbdc0375d65". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "1382cee8789651b8ee15fb73019591caf204289c". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "09834bb6436ecbc21a07c5773016bbba96e02278". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "97bff9ea81e2e2006553c07f46686331834391ad". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "f430fd27f1e39e35878859529b7817f7a4957349". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "0e4a9b30ba505ddc9c236b88f91faaea7c4316d9". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "ad7565f1c6bb16f61bc6dc243c09c5c3e4eca32b". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "a84a85153d98d55f4d2448c8e83d9a35c5284d7f". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "98b327308e719db586f11f9c851bae3dffa52a51". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "dd004ea96c6412fd1f849a88d752733c0a9cacd0". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "6d4cd252796861ebc326e0c982cf01dfcee468fa". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "d30fbb01a973cc0ca754cdc0bbad11c769052023". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "d9ca369997d77f28ffe5a26759eccb781a27405b". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "58dbd1912693c8e28d96905974dc5f164b0c5a48". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "9f99b298176fe8ef6c42ae3578df173643b15d97". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "5152868cf84bed5f234d7eab5ce9a71c902dd975". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "78c9ba3c43b15342a3c42c548c3003b18172ae9e". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "832449db277e7e3e453fb38cd5f066c726f218d9". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "bd5df4b14b25e02d1f78992cef8c457f4ac1cda4". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "2db3e709bc960ba80cd16aaa0127580889eb6b18". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "a62ed8d14b3e3daef5d400a5ae9788f80e8213b9". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "caace7c8a577e4b5251928289a7a97cdf243aab5". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "03fb61596816370ed180fee31707efb22ef5a465". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "85b5b96849f05045735f978dfe81e738876ddd03". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "aadd3f4e5e30be0bd2b37eb0f8c14cd90acdca0b". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "f89a1881bb58bb704c3f88d85631e8c62fdaf17b". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "d421ff5b1f786e3ff7709580a2d6e1b203570703". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "c188955a3aca0c97ef88a79f2c4c5b1158877c87". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "22ab4eafe303e86c06b88d83e46e1e4b5fa072cc". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "f336f64bb066d607f8c8f0bbbe856004cd16297c". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "e143f9e007930ea0a28ada9fd2f0040bec757430". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "3b56716e8189ddb98b9e619450432673f60d918a". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "7be6cbf3ea60fa96fc905bf0590867097acb850e". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "9ad0062a0c912c088b46b394a35c4b0b30c9a477". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "1a82f857e3ce4d91659e5e6ca4631759ea319b3c". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "49d0f54aae0649fef6889935f1506590eca18b25". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "765a14343aaa3993c1ddad08871cef3abcacf1fd". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "79d4dbb67e1fab9c71d85fd47826ed97a6374683". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "16cdbc97c89ff88a7102ac4f57be28d55e4d29da". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "543a80eab5e8d1849578ecf591cb517876ad506d". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "e21fc791370e1e6d4fb8159107aef44f94db8d14". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "066d0187a78ce488a283506a164fe8fff2f875e6". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "2158e07151b984534b1b6bd61ea68a82a6cf787e". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "724ca5bb0f7cd9a1126fada1369435454d227fc8". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "f3315c6411972c6ba6e53fce51da311fadd8b7ab". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "126545170012bc1843c9869d706dafeb26147d06". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "aec190797ed4af10983866c54f554d95246f2b2b". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "a75a81d05b7da2cfb83711fb7a94cdb355d3d75b". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "325928a333fb999fce61c5e369bc4aa99d7cb1f7". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "e81d4ac5fb1e297d52d39089d4f25be26550f3e7". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "c60e2646046dedde8fd393d1d7d42ee7c5c0967d". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "dadb319a80c33b66d5d5ee07548e6c6cbc41ba5f". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "423983acf262a9c7fa93ac8eb726c34276dce7f4". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "806aa6377e2260a17488cac065192767600f108e". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "d0e4cbbb27c2847649e937b49cb791fec234c19d". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "52bcb9bef5451577a83b8f05698926a7a66b0a50". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "a701389b6fbf962fff37d7f626122577e853a785". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "184970ab15fdd8ebf97d99e7cbd6f2632461e436". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "868fafe4f84a8157799ce3d0d2435a0d3cc89d7d". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "4782520733f50e186d38d2de081dd18afe54c9f3". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "cd2e3ff1b548c13bbbe91163004ff427f9948751". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "9f115c2695fae4dc3cd4a6b03e96842005dfe348". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "bdb5346fec8dae23607f9ae21405960845394a2c". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "36dffc7d1bfc50ed5e82d13b92a9fc20b872f2e1". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "e3f1f8dafef868466b9faf0c5be141fd1ee05faf". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "e409375d7fec7899d948c9604bcf580b22f0ea39". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "1d01f0c30a5b07c30e4ea3900a29ac009e09ada9". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "9f5b0667df304746ebe4e9990286a63a5882644a". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "1629d5eb74a109617ca49add8d5c68f2733f15e2". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "d98699b4590ceee3ded10b142ebcfc5e9027eda0". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "275a9930ff99a37fe33208cad32eb9cc4efb559b". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "a697df308fe4168ea1f75d6f42e63dd7d9ab186a". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "ebaf996c71ca26c729f0d6650d31c0158367acc6". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "a250bd3362b1ae5321910d0fcdf07177fd481205". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "4afa55c0b60f6360b4c38640cfe17bf4a65865a8". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "1a4c77cd002b4a03dfcf2f4ab9cacedc16b0f3e1". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "941fbeb8e1e30cd9e03bfbd764173fac00b20bb8". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "397a42d4daca98e6cdbfb144df12b0d82c8f85bb". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "68b9ac96fa44b3c7f7d6f68cd154841822a426bf". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "dcfe8a55f9508cdda480ddda854d6138535f94ae". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames ⚠ "next start" does not work with "output: standalone" configuration. Use "node .next/standalone/server.js" instead. ⚠ "next start" does not work with "output: standalone" configuration. Use "node .next/standalone/server.js" instead. Error: Failed to find Server Action "x". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "x". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "x". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames ⚠ "next start" does not work with "output: standalone" configuration. Use "node .next/standalone/server.js" instead. ⚠ "next start" does not work with "output: standalone" configuration. Use "node .next/standalone/server.js" instead. Error: Failed to find Server Action "x". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "x". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames Error: Failed to find Server Action "x". This request might be from an older or newer deployment. Read more: https://nextjs.org/docs/messages/failed-to-find-server-action at ignore-listed frames