Open hamlim opened 1 month ago
The error is slightly different but still present in the latest canary (15.0.0-canary.173
):
docs:dev: $ next dev --turbo
docs:dev: ▲ Next.js 15.0.0-canary.173 (turbo)
docs:dev: - Local: http://localhost:3000
docs:dev:
docs:dev: ✓ Starting...
docs:dev: ✓ Ready in 2.8s
docs:dev: ✓ Compiled / in 4ms
docs:dev: ✓ Compiled /_error in 0ms
docs:dev: ⨯ [Error: Next.js package not found
docs:dev:
docs:dev: Debug info:
docs:dev: - Execution of *get_written_endpoint_with_issues failed
docs:dev: - Execution of *PagesProject::to_endpoint failed
docs:dev: - Execution of *PagesStructureItem::new failed
docs:dev: - Execution of *FileSystemPath::join failed
docs:dev: - Execution of get_next_package failed
docs:dev: - Next.js package not found] {
docs:dev: name: 'TurbopackInternalError'
docs:dev: }
docs:dev: [Error: Failed to write app endpoint /page
docs:dev:
docs:dev: Caused by:
docs:dev: - Next.js package not found
docs:dev:
docs:dev: Debug info:
docs:dev: - Execution of get_written_endpoint_with_issues failed
docs:dev: - Execution of <AppEndpoint as Endpoint>::write_to_disk failed
docs:dev: - Failed to write app endpoint /page
docs:dev: - Execution of AppEndpoint::output failed
docs:dev: - Execution of *get_app_page_entry failed
docs:dev: - Execution of *ModuleAssetContext::new failed
docs:dev: - Execution of get_server_module_options_context failed
docs:dev: - Execution of get_transpiled_packages failed
docs:dev: - Execution of *FileSystem::read failed
docs:dev: - Execution of *FileSystemPath::fs failed
docs:dev: - Execution of *FileSystemPath::join failed
docs:dev: - Execution of get_next_package failed
docs:dev: - Next.js package not found] {
docs:dev: name: 'TurbopackInternalError'
docs:dev: }
docs:dev: ⨯ [Error: Next.js package not found
docs:dev:
docs:dev: Debug info:
docs:dev: - Execution of *get_written_endpoint_with_issues failed
docs:dev: - Execution of *PagesProject::to_endpoint failed
docs:dev: - Execution of *PagesStructureItem::new failed
docs:dev: - Execution of *FileSystemPath::join failed
docs:dev: - Execution of get_next_package failed
docs:dev: - Next.js package not found] {
docs:dev: name: 'TurbopackInternalError'
docs:dev: }
docs:dev: [Error: Next.js package not found
docs:dev:
docs:dev: Debug info:
docs:dev: - Execution of *get_written_endpoint_with_issues failed
docs:dev: - Execution of *PagesProject::to_endpoint failed
docs:dev: - Execution of *PagesStructureItem::new failed
docs:dev: - Execution of *FileSystemPath::join failed
docs:dev: - Execution of get_next_package failed
docs:dev: - Next.js package not found] {
docs:dev: name: 'TurbopackInternalError'
docs:dev: }
docs:dev: ✓ Compiled /favicon.ico in 0ms
However also notably there is something shown in the browser where as there was nothing returned before (now it shows the generic Internal Server Error
page).
Link to the code that reproduces this issue
https://github.com/hamlim/deno-monorepo
To Reproduce
deno upgrade rc
(using at least2.0.0-rc.7
)deno install
to install dependenciesdeno task dev --filter=docs
(runs the docs Next app in development mode)localhost:3000
Current vs. Expected behavior
Following the above steps - I'd expect the app to boot correctly, however it instead shows the following error in the terminal:
Note:
Removing
--turbo
on the dev task withinapps/docs/package.json
makes it work as expected.My assumption is that turbopack (maybe) is unable to resolve the symlinked
next
package from the rootnode_modules
(next is installed somewhere else withdeno
and then symlinked I think)Provide environment information
Which area(s) are affected? (Select all that apply)
Module Resolution, Turbopack
Which stage(s) are affected? (Select all that apply)
next dev (local)
Additional context
Will attempt to replicate with the latest canary!