no idea, with socket.io below 4.0.2 it works, with 4.1.x it throws this Error: unknown packet type NaN
See original GitHub issueSorry, it is a simple error:
Uncaught Error: unknown packet type NaN
at Decoder.decodeString (index.js:151)
at Decoder.add (index.js:105)
at Manager.ondata (manager.js:199)
at Socket.Emitter.emit (index.js:145)
at Socket.onPacket (socket.js:399)
at WS.Emitter.emit (index.js:145)
at WS.onPacket (transport.js:105)
at WS.onData (transport.js:98)
at WebSocket.ws.onmessage (websocket.js:111)
Issue Analytics
- State:
- Created 2 years ago
- Reactions:4
- Comments:8 (2 by maintainers)
Top Results From Across the Web
How to resolve a Socket.io 404 (Not Found) error?
If you're running Express 4, it appears to me like you're missing the lines of code: var app = express(); var server =...
Read more >MySQL Connector/J
Connector/J 5.1 is the Type 4 pure Java JDBC driver, which conforms to the JDBC 3.0 and JDBC 4.0 specifications. It provides.
Read more >Repository
Fix for Bug#71753 (18260918), Bad SSL socket transform. - Added tests for changes in GET DIAGNOSTIC syntax introduced in MySQL 5.7.0. - Fix...
Read more >Appendix C. MySQL Change History
cnf if necessary to specify the desired log file configuration. Then upgrade to MySQL 5.4.3 and start the new server. mysqld sees that...
Read more >News – collectd – The system statistics collection daemon
SNMP plugin: Error handling has been improved: a potential double-free is now avoided (potentially leaking memory) and handling of non-failing subtrees has ...
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 FreeTop 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
Top GitHub Comments
I could indeed reproduce, we will publish a fix as soon as possible.
yes, i can verify the error is gone and it works as expected.