It appears since 2.0.1, multi-byte characters are breaking in browser clients.

In practice, we have an application that happened to send a JSON message containing a no-break space (U+00A0) somewhere, and the browser client received the message with the final } cut-off.

With a normal install of [email protected], zuul tests also fail there. When the engine.io-parser dep is then replaced with 2.0.0 (by simply swapping the directory in node_modules), tests succeed again.

All tests seem to work fine in Node.js.

(macOS 10.12.3, Chrome 56.0.2924.87. Same results in Firefox 52.0.)