Next.js v14.0.0 server with socket.io client doesn't send messages with more than a few characters about socket.io-client HOT 5 OPEN

With debugging -

Pass (abc)

Fail (abcd)

The only difference is engine.io-client:websocket displaying websocket closed before onclose event at then end.

Heartbeat is still working afterwards.

from socket.io-client.

Here is a github repo to reproduce the error https://github.com/mecabricks/debug-socketio

To Reproduce

1. yarn dev-ws
2. yarn dev
3. Make a GET request to the page http://localhost:3000/api/test
4. See the logs in the socket.io server terminal window

Current vs. Expected behavior
The socket.io server shall receive the 3 messages sent by the socket.io client (server side) however only two are received - The two with the same length. The longest is not sent over the network.

socket.emit("partLibraryIconEvent", { test: "abc" });   // OK
socket.emit("partLibraryIconEvent", { test: "abcd" });  // NOT OK
socket.emit("partLibraryIconEvent", { test: "123" });   // OK

from socket.io-client.

Experiencing the same, had to move all server code using websockets back to pages dir api routes.

I'm wondering why the websocket gets closed. Do we need to set some extra response headers on routes using websockets? Is this even a socket.io issue or a next.js issue?

from socket.io-client.

I believe that NextJS is overwriting something when packing the code. We cannot figure out what.
However, the solution that I just found is to exclude the socket.io-client package from webpack on the server.

Here is the code to go in next.config.js

webpack: (config, { isServer }) => {
  isServer && (config.externals = [...config.externals,  'socket.io-client']);
  return config;
},

from socket.io-client.