-
Notifications
You must be signed in to change notification settings - Fork 66
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
Quasar, Vite, Cypress out-the-box config hanging on Node 18 #236
Comments
Seems like a problem with Node 18, as I cannot reproduce it on Node 14 or 16 Thanks for reporting anyway, we'll work on this later on |
I'm pretty sure there was a reason why I didn't go with |
@KrisCarr, @IlCallo, @mv-go, I have faced the same issue in my project/setup, but I've also found a different workaround: put the |
I just tried it out again today and could not reproduce with this setup Ubuntu: 22.04 Is this an issue only on Windows/Mac? |
@IlCallo, it might be, but it should probably be confirmed by somebody else (more testers needed). |
@IlCallo I have re-tested and can confirm it is still an issue at least on macOS with M1 chip (don't have access to another machine at the moment to test others). I first tried with Node 18.12.0 that was currently installed then updated to 18.14.2 Updated reproduction commands:
This then hangs silently in a retry loop failing to connect to ::1, it does eventually give up after quite a while: Running this shows the verbose output showing the underlying attempts: Output:
Full output from command execution to the above (attached to save space): |
I have the exact same problem with:
In my case the error reported is: Error: Timed out waiting for: http-get://localhost:4444 Reverting to Node.js 16 solves this. |
Hey there, did anyone test this on latest versions of Node 18 or even Node 20? |
A guy on Discord tested with Node 20 on Windows and apparently it works on that version |
I'm on a Mac (13.5.2) using Node 20 and Cypress 13, the fix for me was replacing |
This seems to be the culprit: nodejs/node#47785 Node <18 resolved localhost to 127.0.0.1, while Node >= 18 (on Mac for sure, and on Windows for Node 18 for sure) resolve to its IPv6 counterpart ::1 |
As expected, took me quite a while to properly understand issue root and test the fix If you're curious about the backstory, check these links out: 8552ba3#diff-0df604707cf8f7ef7a25247848b4f8ef0383458d0138fb6e50af9f8d17554079R84-R95 TL;DR: Node 18 did a mess with |
Well done, @IlCallo! Thank you! ❤️ |
Thank you for your patience 😁 |
Software version
OS: Macos / Windows 10
Node: 18.2.0
NPM: 8.10.0
Any other software related to your bug:
What did you get as the error?
running the generated script
test:e2e
ortest:e2e:ci
causes a hang. Upon adding the debug environment variable forstart-test
it is getting a connection refused on ::1What were you expecting?
Cypress to start
What steps did you take, to get the error?
yarn create quasar
choosingvite
.yarn test:e2e
oryarn test:e2e:ci
Current fix / workaround
It appears the generated scripts in
package.json
tellstart-test
to listen forhttp-get://localhost:9000
which is resolving to::1
at runtime. This is not listened on byquasar dev
out-the-box.The current fix is to change the script to listen for
http-get://127.0.0.1:9000
to force ipv4 or to change the listen address for the dev server.The text was updated successfully, but these errors were encountered: