Firefox HMR error in console
See original GitHub issueBug report
Describe the bug
Loading any page in firefox shows this error in the console:
The connection to http://localhost:3000/_next/webpack-hmr was interrupted while the page was loading.
To Reproduce
git clone git@github.com:zeit/next.js.gitcd next.js/examples/blog-starternpm installnpm run dev- Visit localhost:3000 and open console.
- See
The connection to http://localhost:3000/_next/webpack-hmr?page=/ was interrupted while the page was loading.
Expected behavior
This error should not happen
Screenshots
System information
- OS: Mac OS Catalina
- Firefox Developer
- Version of Next.js: 9.1.6
Additional context
Issue Analytics
- State:
- Created 4 years ago
- Reactions:6
- Comments:5 (3 by maintainers)
Top Results From Across the Web
Firefox HMR error in console #23647 - gatsbyjs/gatsby - GitHub
Clone a website - like gatsby starter. Open in Firefox (I'm using developer edition); View the console error. Environment. System: OS: macOS ...
Read more >Nuxt Firefox console errors webpack hmr - Stack Overflow
It appears in Firefox developer edition when I run the npm run dev command for localhost. The connection to http://localhost:3000/__webpack_hmr ...
Read more >Webpack hot reloading broken in Firefox Developer Edition
Hi, I've just switched to Firefox Developer Edition for my dev work. ... Is the page not hot-reloading or is it just the...
Read more >How to fix console errors? | Firefox Support Forum
The content blocking error is because you are using trackers on your website that Firefox blocks by default.
Read more >Console messages — Firefox Source Docs documentation
If a line that generates a warning or error is executed more than once, ... For JavaScript, CSS and console API messages, the...
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 Free
Top 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

This is because you had a serviceworker installed on localhost:3000 from a project that isn’t using Next.js.
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.