Open mjomble opened 3 days ago
1.1.36+ededc168c
Microsoft Windows NT 10.0.22631.0 x64
Script 1:
import { createServer } from 'node:net' const server = createServer() server.listen('\\\\.\\pipe\\test')
Script 2:
import { createServer } from 'node:http' const server = createServer((req, res) => res.end('ok')) server.listen('\\\\.\\pipe\\test')
Script 3:
Bun.serve({ unix: '\\\\.\\pipe\\test', async fetch() { return new Response('ok') }, })
All three scripts execute successfully and start listening on the socket without throwing any errors.
Script 1 succeeds.
Scripts 2 and 3 both fail with
ENOENT: No such file or directory errno: -2 syscall: "listen" path: "\\.\pipe\test"
No response
AF_UNIX is currently support by Bun.serve but not named pipes yet. Named Pipes is missing support on node:http and currently supported on node:tls, node:net and node:http2
node:http
node:tls
node:net
node:http2
What version of Bun is running?
1.1.36+ededc168c
What platform is your computer?
Microsoft Windows NT 10.0.22631.0 x64
What steps can reproduce the bug?
Script 1:
Script 2:
Script 3:
What is the expected behavior?
All three scripts execute successfully and start listening on the socket without throwing any errors.
What do you see instead?
Script 1 succeeds.
Scripts 2 and 3 both fail with
Additional information
No response