Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Nuxt Websocket connection issues #16447

Open
felixrydberg opened this issue Jan 16, 2025 · 0 comments
Open

Nuxt Websocket connection issues #16447

felixrydberg opened this issue Jan 16, 2025 · 0 comments
Labels
bug Something isn't working needs investigate Needs to be investigated to find the root cause web:websocket

Comments

@felixrydberg
Copy link

What version of Bun is running?

1.1.42+50eec0025

What platform is your computer?

Linux 6.8.0-41-generic x86_64 x86_64

What steps can reproduce the bug?

Bug is that when running Nuxt with Node both Http & Websocket requests are able to call API endpoints while using Bun only Http requests are able to call API endpoints

I have created a repository with all the setup.

https://github.com/felixrydberg/bun-npm-nuxt-websocket-mismatch

What is the expected behavior?

I would say the same way that Node handles it, where both a websocket and Http call will both get captured by the the catch all route

What do you see instead?

When using Bun only Http requests gets caught while using Node both Websocket and Http requests get caught.

Additional information

No response

@felixrydberg felixrydberg added bug Something isn't working needs triage labels Jan 16, 2025
@DonIsaac DonIsaac added needs investigate Needs to be investigated to find the root cause web:websocket and removed needs triage labels Jan 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs investigate Needs to be investigated to find the root cause web:websocket
Projects
None yet
Development

No branches or pull requests

2 participants