Fix default server host value causing issues on Windows (#27306)
This fixes a case where the HMR connection for fast refresh would fail to connect on Windows due to a change being made to the default host being listened to. Previously we didn't set a default for the `host` value when calling `server.listen` which allowed the default listening behavior to be used although in https://github.com/vercel/next.js/pull/20409 a default of `0.0.0.0` was added which causes conflicts for some set-ups mainlly on Windows it seems. ## Bug - [x] Related issues linked using `fixes #number` - [ ] Integration tests added (N/A) - [x] Errors have helpful link attached, see `contributing.md` Fixes: https://github.com/vercel/next.js/issues/27298 Fixes: https://github.com/vercel/next.js/issues/27254 Fixes: https://github.com/vercel/next.js/issues/4456#issuecomment Fixes: https://github.com/vercel/next.js/pull/20409#issuecomment-849933092 x-ref: https://github.com/vercel/next.js/pull/20409
Showing
Please
register
or
sign in
to comment