Skip to content

fix: resolve Windows daemon connection issues#542

Open
dongliang wants to merge 1 commit intovercel-labs:mainfrom
dongliang:fix/windows-daemon-connection
Open

fix: resolve Windows daemon connection issues#542
dongliang wants to merge 1 commit intovercel-labs:mainfrom
dongliang:fix/windows-daemon-connection

Conversation

@dongliang
Copy link

On Windows, std::path::Path::canonicalize() returns extended-length paths with \\?\ prefix. Node.js cannot handle these paths, causing the daemon to fail to start.

This PR fixes two issues in cli/src/connection.rs:

  1. Strip the \\?\ prefix from canonicalized exe path on Windows, so Node.js can correctly resolve the daemon binary
  2. Use platform-specific info in the daemon startup error message — show TCP port on Windows instead of Unix socket path

1. [Strip \?\ path prefix]: Strip the extended-length path prefix from canonicalized exe path on Windows, as Node.js cannot handle \?\ prefixed paths
2. [Platform-specific daemon error message]: Replace hardcoded socket path in daemon startup error with platform-aware info — show TCP port on Windows, socket path on Unix
@vercel
Copy link
Contributor

vercel bot commented Feb 25, 2026

@dongliang is attempting to deploy a commit to the Vercel Labs Team on Vercel.

A member of the Team first needs to authorize it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant