-
Notifications
You must be signed in to change notification settings - Fork 41
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
Add support for React NextJS #268
Comments
I guess you would need to configure next js to use 3000 for websocket (instead of 8080) like we do with vite. |
That might help: vercel/next.js#6271 |
I will test today and it it works I will submit a PR for the docs in case anyone else wants to use Next! |
OK it looks like that post for configuring the websocket was from 2019 and they removed it with this PR: vercel/next.js#6354 It looks like they don't allow control of that websocket port they use something called Event sourcing? I submitted this: vercel/next.js#47000 |
Ahhh I see you have already discussed this exact issue: #71 |
Reproducer project:
quinoa-nextjs.zip
NextJS serves on port 3000 like Create React app does and it does not serve an index.html but I have Quinoa configured where it almost works.
If you run
mcn quarkus:dev
on the above project the one remaining issue is that NextJS opens a websocket this works normally and returns a 101.But in Quinoa its return a 403 and tries over and over again. I believe Next JS needs this socket open to communicate changes
GET /_next/webpack-hmr HTTP/1.1
If we can get this working I would be happy to submit a PR to update the documentation.
The text was updated successfully, but these errors were encountered: