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
No matter if client-side or server-side, if I open a new websocket, it does not pass through the handle hook.
More documentation on the websockets implementation would be helpful, as the bun documentation only partially extends this documentation.
Using the exact code from the example in the readme, in dev, preview and build. e.g.:
const ws = new WebSocket(
wsURL
);
The text was updated successfully, but these errors were encountered:
I ran across the same thing. Diving into the code, there's a hack at the button of /index.js which rewrites handleWebsocket to be this.websocket = -- but I can't find where it's creating the Bun websocket etc.
Try building for production (bun run build, bun run build/index.js) then connect to Websocket on the default port 3000. (has to be /ws by default : ( if (url.pathname.startsWith('/ws')) { )
From other sources on the web, for this to work in development mode we'll need to create a Vite plugin. Not sure how to do that yet.
(Also changing output directory is useful since bun will help since bun will refuse to run the script in package.json if build/index.js exists.)
No matter if client-side or server-side, if I open a new websocket, it does not pass through the handle hook.
More documentation on the websockets implementation would be helpful, as the bun documentation only partially extends this documentation.
Using the exact code from the example in the readme, in dev, preview and build. e.g.:
const ws = new WebSocket(
wsURL
);
The text was updated successfully, but these errors were encountered: