Open SupertigerDev opened 6 months ago
1.1.18
Microsoft Windows NT 10.0.22631.0 x64
import express from 'express'; import { createServer } from 'http'; import { Server } from "socket.io"; const app = express(); const server = createServer(app); const io = new Server(server, {transports: ["websocket"]}); app.get('/', (req, res) => { res.send(` <script src="https://cdn.socket.io/4.7.5/socket.io.min.js"></script> <script> const socket = io("http://localhost:3000", { transports: ["websocket"] }); </script> `); }); io.on('connection', (socket) => { console.log("connected", socket.handshake.address) }); server.listen(3000, () => { console.log('listening on http://localhost:3000'); });
bun i express socket.io
It should consistantly log connected ::1 just like it does in nodejs
connected ::1
I see that it sometimes logs undefined
undefined
It may be a Windows only issue, not sure.
Just want to confirm that this issue is still happening on version 1.1.18
What version of Bun is running?
1.1.18
What platform is your computer?
Microsoft Windows NT 10.0.22631.0 x64
What steps can reproduce the bug?
bun i express socket.io
What is the expected behavior?
It should consistantly log
connected ::1
just like it does in nodejsWhat do you see instead?
I see that it sometimes logs
undefined
Additional information
It may be a Windows only issue, not sure.