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
One implementation could be: wait-on (tcp:[::1]:80 tcp:127.0.0.1:80)
Alternatively, it could be pure config.
If I've misread the docs and this already exists, then my apologies.
Issue I'm solving:
Since updating to Node17+. Node DNS lookups return IPv6 first. Which might not seem like a massive issue, but localhost URLs are now in theory [::1]:{port} rather than 127.0.0.1:{port}
My current project is using wait on like so - wait-on localhost:5000 localhost:5001 and will hang as the servers are starting on [::1]:5000 ... etc..
The text was updated successfully, but these errors were encountered:
Adding my two cents, I think would be better to make wait-on do listen on both IPv by default when it encounters a localhost origin within the resources passed through, at least until nodejs/node#44731 gets merged.
But the OR feature will be indeed a good addition.
A nice to have would be the ability to OR URLs.
One implementation could be:
wait-on (tcp:[::1]:80 tcp:127.0.0.1:80)
Alternatively, it could be pure config.
If I've misread the docs and this already exists, then my apologies.
Issue I'm solving:
Since updating to Node17+. Node DNS lookups return IPv6 first. Which might not seem like a massive issue, but
localhost
URLs are now in theory[::1]:{port}
rather than127.0.0.1:{port}
My current project is using wait on like so -
wait-on localhost:5000 localhost:5001
and will hang as the servers are starting on[::1]:5000
... etc..The text was updated successfully, but these errors were encountered: