Repository navigation
Unix Domain Socket doesn't support on Windows #55979
Description
Activity
OP is aware this needs to happen in libuv first, see libuv/libuv#2537 (comment) and note the unsubstantiated performance claim.
- addedwindowsIssues and PRs related to the Windows platform.Issues and PRs related to the Windows platform.libuvIssues and PRs related to the libuv dependency or the uv binding.Issues and PRs related to the libuv dependency or the uv binding.
on Nov 24, 2024 About performance I'll leave some extra into there.
github-actions commented
on Apr 26, 2026 on Apr 26, 2026 – with GitHub ActionsContributorMore actionsThis issue has been marked as stale due to 210 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.Reacted by Ravi van Rooijen- addedstaleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.
on Apr 26, 2026 This issue is still relevant today. Since VSCode extensions are running on nodejs, implementing Language Server connectivity through domain sockets is currently blocked. This aspect is active part of the considerations around godotengine/godot-proposals#13490
You could try push on merging libuv/libuv#4636 :)
Reacted by Ravi van Rooijen and Andrei Moiseev- removedstaleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.
on Apr 28, 2026 github-actions commented
on Jul 28, 2026 on Jul 28, 2026 – with GitHub ActionsContributorMore actionsThis issue has been marked as stale due to 90 days of inactivity.
It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.- addedstaleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.
on Jul 28, 2026 This issue is still relevant today. Since VSCode extensions are running on nodejs, implementing Language Server connectivity through domain sockets is currently blocked. This aspect is active part of the considerations around godotengine/godot-proposals#13490
- removedstaleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.Issues and PRs marked stale due to inactivity and scheduled for automatic closure.
on Jul 29, 2026 - added 2 commits that reference this issue
on Sep 13, 2026
Version
20.18.0
Platform
Subsystem
No response
What steps will reproduce the bug?
Currently, Windows (at least .NET) supports connect to UnixDomainSocket, or listen to UnixDomainSocket in ASP.NET Core. But node's net module seems not support connect to a Windows local file.
How often does it reproduce? Is there a required condition?
Always
What is the expected behavior? Why is that the expected behavior?
The net connects to the "Windows" UnixDomainSocket as it could.
What do you see instead?
EACCESS / ENOENT
Additional information
No response