You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
OP is aware this needs to happen in libuv first, see libuv/libuv#2537 (comment) and note the unsubstantiated performance claim.
bnoordhuis
added
windows
Issues and PRs related to the Windows platform.
libuv
Issues and PRs related to the libuv dependency or the uv binding.
labels
Nov 24, 2024
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
The text was updated successfully, but these errors were encountered: