-
Notifications
You must be signed in to change notification settings - Fork 5
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
Not working with SSR enabled #23
Comments
That doesn't really tell me much. There's an event handler that catches errors so if that's not outputting anything I'm not sure I can assist. |
Thanks for the reply, |
Ah yea there's an issue with useFetch that caused me to make another module because it's a pain to have to try to make it work with the proxy module. This module was originally able to handle $fetch/useFetch but i had long since removed it because it got incompatible after an update and playing cat/mouse with this framework was annoying. So you have 2 options here:
In regards to the websockets which was what you were originally looking for I have yet a third module: https://github.com/nuxt-alt/websocket you can read it and see what I had to do to get things working... The fix is relatively simple in regards to the framework, but because it's been months with no ws support I just threw that together, but ultimately it's not as good as just having ws support in the first place or at least being able to get the server instance from nitro. |
Maan that's a lot of headache, thanks for the options. I indeed needed a proxy for websockets since nitro still doesn't include it... |
@JoniLieh can you try using |
Thanks for the quick update, unfortunately nothing has changed for me... |
Any updates on this? I'm still having the problem |
Idk I abandoned my websocket proxy idea... mb https://nuxt.com/modules/api-party will help idk if they support ws tho |
Hello and thanks for this awesome package!
I have a problem when ssr is enabled, the webpage takes forever to load and nothing happens.
In the console there is
/ -> http://localhost:3001/
I think this looks good tho.I tested it with
ssr: false
→ works,ssr: true
→ doesn't work. (same goes for ws)The text was updated successfully, but these errors were encountered: