Closed rstacruz closed 8 years ago
Also relevant:
This is how engine.io-client fixed it in their package: https://github.com/socketio/engine.io-client/pull/451/files
hmm, okay, it seems a socket.io-client
fix was deployed just yesterday. If anyone else is running into this, you'll have to delete socket.io-client and npm install
again.
Thanks for pointing out that a problem existed.
My response was going to be to see if pinning to an old version of socket.io-client
worked until they fixed the issue themselves. Good to see they've done that now.
Aye, it really was a headache, pretty much busted every npm consumer of socket.io for a few days :\
Using browserify-hmr now gives you these errors:
Because
ws
is now not compatible with browserify:This is a problem because
browserify-hmr
usesws
, which it assumes to be browserifyable (it was before!). As a workaround, you can installbufferutil
andutf-8-validate
, but it probably won't work completely (they rely on compiled extensions), and it will add 3.5MB of bloat on your package.