-
Notifications
You must be signed in to change notification settings - Fork 27k
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
Error on reloading page in the initial next.js installation #4456
Comments
I got another error
|
Sounds like you have a babelrc in a directory above the next.js app, next itself doesn’t use babel-preset-react-app, that’s a create-React-app preset |
Hey @RobertB4 did you find a workaround? |
I'm going to close this as it's probably outdated and fixed already if there was an issue before. |
Hello, October 2019 here, I still have this error with a lightly different message : Anyway to clean a bit the console in dev mod? Thanks |
Bump, same problem here. Next 9.1.1 |
Same, only with firefox. |
Same problem, only with Firefox too |
@timneutkens can this issue be reopened? Or should we create a new one, separate for Firefox issues? |
Getting this on firefox too. Good news is that soon firefox will be able to negate things from the filter with "-webpack" - but not yet :( |
I've created a new issue for this: |
having similar error hot reload do not works (no updating triangle) issue happens from version 10.0.5 and greater, versions from 10.0.0 to 10.0.4 are working ok, I was able to downgrade and work normally it is strange but looks like it is only browsers (tested Chrome and Firefox on two diffrent machines) cannot perfom request, commands like wget or curl do receive data |
Hey bfunc I had similar issue and removing an old registered service-worker solved my problem, please take a look --> #9776 (comment) |
I resolved this by removing the
|
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 #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: #27298 Fixes: #27254 Fixes: #4456 (comment) Fixes: #20409 (comment) x-ref: #20409
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 vercel#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: vercel#27298 Fixes: vercel#27254 Fixes: vercel#4456 (comment) Fixes: vercel#20409 (comment) x-ref: vercel#20409
This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Describe the bug
I get the following error shown in the console when I reload a page in firefox:
The connection to http://localhost:3000/_next/webpack-hmr was interrupted while the page was loading.
This seems to happen even with a new next.js installation.
To Reproduce
mkdir nextjs-test
npm install --save next react react-dom
"dev": "next"
./pages/index.js
and copy the following code:export default () => <div>Welcome to next.js!</div>
npm run dev
and open localhost:3000 in firefox.Expected behavior
I expect no error since I only followed the basic setup.
System information
The text was updated successfully, but these errors were encountered: