Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Next.js development HMR should use a higher-limit browser communication channel

See original GitHub issue

Next.js’ development pages currently use EventSource to communicate with the development server. These connections are typically imposed a limit of 5 by the browser, making it incompatible with applications like Sizzy.

This also affects users who open more than 5 tabs in their browser connecting to the dev server.

We should use a WebSocket or alternative API that is given a higher limit by the browser.

Issue Analytics

State:
Created 4 years ago
Reactions:2
Comments:5 (5 by maintainers)

Top GitHub Comments

1reaction

Janpotcommented, Jul 22, 2019

For reference https://github.com/zeit/next.js/pull/6354. I think there were too many issues with the Websocket implementation. Another thing that could be explored is to multiplex a single EventSource that lives in a SharedWorker over the different tabs. But that might be easier said than done 🙂

Edit:

It looks like there’s some prior art around this, but the repository seems to be deleted.

0reactions

balazsorban44commented, Jan 30, 2022

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.