HRM hot file use IPv6 while vite devserver running on IPv4
See original GitHub issue- Laravel Vite Plugin Version: 0.5.0
- Laravel Version: 9.21.4
- Node Version: 18.3.0
- NPM Version: 8.11.0
- Host operating system: macOS Monterey 12.4
- Web Browser & Version: Chome 103.0.5060.114 (arm64)
- Running in Sail / Docker: No (Valet)
Description:
HRM hot file use IPv6 while vite devserver running on IPv4
The URL inside public/hot
file: http://::1:5173
Steps To Reproduce:
Upgrade from 0.4.0 and vite 2.9.9, then starts the dev server with npm run dev
Issue Analytics
- State:
- Created a year ago
- Comments:11 (6 by maintainers)
Top Results From Across the Web
vite server listen on IPv6 only · Issue #2032 - GitHub
I tried server.host option, looks like it only changed "Vite dev server running at" tips, server still listen on IPv6.
Read more >A way to run vite dev on remote server (like Laravel Mix)
If I run npm run dev with Vite it revs up the "dev" server that's supposed to be at http://ip:3000, but that obviously...
Read more >Expose local Vite instance to the network - Amit Merchant
Now, when you spin this dev instance up by running the npm run dev , here's what ... The --host option; The Vite...
Read more >Untitled
#Product 2 street 5k run philadelphia, Arti dari penampahan galungan, Rc-l01 remote guidance unit, Thursday movie dallas, Scienze politiche palermo sito!
Read more >Tilde Chat Corpus (raw)
:cdmnky!cdmnky@tilde.team PRIVMSG #meta :let's vote on it in november lol ... when the only thing we're using from there is Scanner?
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Taking a look over the changelog I can see that this was released (as shown above) in Node
v18.4.0
.Issue: https://github.com/nodejs/node/issues/43014 Pull Request: https://github.com/nodejs/node/pull/43054
Seems changing this was essentially seen as a bug fix as it was breaking many 3rd party packages, thus it was pushed in a minor release.
Please update to at least node
v18.4
. We may consider putting a patch in place for this, but for now updating should get you out of trouble.I found this after doing some research https://nodejs.org/api/net.html#serveraddress. Definitely interesting!