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.

Using MSW with Next.js causes stopping HMR/Fast Refresh

See original GitHub issue

Describe the bug

Using MSW with Next.js causes stopping HMR/Fast Refresh because of unclosed SSE connections.

Environment

msw: 0.26.2
nodejs: 14.14.0
yarn: 2.4.1
Browser: Chromium 89.0.4389.82

To Reproduce

Steps to reproduce the behavior:

Clone https://github.com/tkamenoko/msw-nextjs-hmr .
Install deps: yarn .
Start dev server: yarn dev .
Open localhost:3000 in your browser.
Show Network tab in DevTools.
Click rendered links, and you will find that SSE connections between MSW and the dev server are not closed.
After the number of connections reaches the limit, HMR will not work.
Reload the page, but it will not complete: Waiting for available sockets

Expected behavior

A browser should receive changes and refresh the page. SSE connections between MSW and the dev server should be closed when connections between browser and MSW are closed.

Issue Analytics

State:
Created 3 years ago
Reactions:2
Comments:18 (9 by maintainers)

Top GitHub Comments

13reactions

khw1031commented, May 11, 2021

Having the same Issue

msw v0.28.2
next v10.1.2

11reactions

saintwinklecommented, Mar 25, 2021

@kettanaito I think what @tkamenoko and I mean is that this issue is tracking HMR issue, not the solved cookies issue which maybe not related to this one.😂 So we can still discuss here.

I’ve created a simpler repo to reproduce the issue: https://github.com/saintwinkle/with-msw-next-app .

And here’s the process:

https://user-images.githubusercontent.com/4580163/112440392-3720df00-8d85-11eb-9646-9b8df73879ef.mov

If i’m missing something, let me know. Thanks!