Skip to content

Conversation

@coofly
Copy link

@coofly coofly commented Feb 1, 2026

Summary

Fix daemon startup failure on Windows when installed globally via npm.

Problem

On Windows, canonicalize() returns UNC path format (\?\C:\Users\...). When the CLI passes this path to Node.js to start the daemon, Node.js cannot correctly handle the UNC path format, causing "Daemon failed to start" error.

Solution

Strip the UNC prefix (\?\) on Windows before passing the path to Node.js.

Testing

  • cargo build passes
  • cargo test passes (148 tests)
  • Verified daemon starts successfully on Windows with global npm install

On Windows, canonicalize() returns UNC path format (\?\C:\Users\...).
When the CLI passes this path to Node.js to start the daemon, Node.js
cannot correctly handle the UNC path format, causing "Daemon failed to
start" error. This fix strips the UNC prefix before passing the path.
@vercel
Copy link
Contributor

vercel bot commented Feb 1, 2026

@coofly 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