Turbopack Error: FileSystemPath("").join(...) leaves the filesystem root

[Ti0Elvis]

Turbopack version: v15.4.0-canary.130
Next.js version: 0.0.0

Error message:

FileSystemPath("").join(...) leaves the filesystem root

Debug info:
- Execution of get_entrypoints_with_issues_operation failed
- Execution of EntrypointsOperation::new failed
- Execution of Project::entrypoints failed
- Execution of Project::middleware_endpoint failed
- Execution of *MiddlewareEndpoint::new failed
- Execution of Project::middleware_context failed
- Execution of *parse_config_from_source failed
- Execution of *ProcessResult::module failed
- Execution of *AssetContext::process failed
- Execution of Project::edge_middleware_context failed
- Execution of AppProject::edge_ecmascript_client_reference_transition failed
- Execution of *NextEcmascriptClientReferenceTransition::new failed
- Execution of AppProject::client_transition failed
- Execution of *FullContextTransition::new failed
- Execution of AppProject::client_module_context failed
- Execution of *ModuleAssetContext::new failed
- Execution of AppProject::client_module_options_context failed
- Execution of *get_client_module_options_context failed
- Execution of Project::execution_context failed
- Execution of Project::node_root failed
- FileSystemPath("").join(...) leaves the filesystem root

[alu-sys]

This seems to be happening to everyone with mono-repos.

[Ti0Elvis]

Uhm... so is normally that error?

[alu-sys]

No. Whatever is happening has been caused by the latest patches. It seems to a problem with users using the Windows platform, as this doesn't occur on Linux.

[alu-sys]

It isn't even resolving the Next.JS version.

[SerbanUntu]

This seems to be happening to everyone with mono-repos.

Happened to me as well

[alu-sys]

This seems to be happening to everyone with mono-repos.

Happened to me as well

You'd expect extensive testing before a patch, but... hey-ho, I'm sure they'll solve it.

[astrodomas]

Experiencing the same issue in nx workspaces

[astrodomas]

resolved in the latest canary

[asim1801]

Yeah same issue here, when I run the exact same codebase in a Linux VM, Turbopack works perfectly and the app starts without issue but when I change the builder to Webpack on Windows, it also works.