RangeError: Invalid WebSocket frame: RSV1 must be clear

[baukevanderlaan]

Hello,

I found that when running a fresh Snowpack setup on port 8080 (which is what Snowpack uses when no config is found) I consistently get a crash when I manually reload the page in the browser or make a change which triggers a hot reload. This is the error I get:

events.js:291
      throw er; // Unhandled 'error' event
      ^

RangeError: Invalid WebSocket frame: RSV1 must be clear

If I add configuration that makes Snowpack run on any other port, the error and crash don't appear.
I'm on MacOS 10.15.7 and don't have Snowpack installed globally.

Let me know if you'd like me to give more details.

[FredKSchott]

Hmm, does this thread help triage the issue at all? websockets/ws#1140

Sounds like something that may only exist in Node v10?

I'd love to fix this, but it sounds like the best we can do is switch the default port and/or handle this error with a better error message explaining that changing the port may help.

[baukevanderlaan]

Thanks for your answer!

For what it's worth: my Node version is 14.9.0

I also found some threads regarding this error in the websockets repository, but what they're discussing (including the thread you linked to) is a bit above my head I'm afraid.

Switching the default port would have my personal preference but documenting this error for others to find would already be very helpful. Let me know if you want me to help with this.

[thm76]

I have the same problem with latest macOS Big Sur (release candidate) and Node version 15.1.0.
If I change the port to something other than the default 8080 it works.

[FredKSchott]

I have no personal attachment to 8080, other than it's a bit of a gray area whether this would be considered a breaking change. I think it may be, unfortunately, which means that we won't be able to fix this until v3.0.

In the meantime, I'd love a PR that adds a special handler for this error, that shows a more clear error message explaining that you should change the port to resolve.

[baukevanderlaan]

Got it. I'm not sure when I can take a look at that error handler, but if it helps I can make a PR soon that mentions this error in the docs (under the chapter Troubleshooting). Would that be appreciated?

[baukevanderlaan]

I went ahead and made a PR that mentions this error in the docs: #1822.
I also noticed that a RC for v3.0 was published recently with plans for a release in January. Any chance a different default port could be used in v3?