Not handling some events using on method, but works fine with onAny method.

[moltar]

  const webSocketClient = getWebSocketClient()

  webSocketClient.removeAllListeners('module_update')

  console.log('b4 module_update')
  webSocketClient.on('module_update', () => {
    console.log('in module_update')
    moduleStore.refreshSummary()
  })

  webSocketClient.onAny((eventName, ...args) => {
    console.log('on any', eventName, args)
  })

I see b4 module_update printed.

When events get emitted, I see module_update being caught by .onAny, but not by the .on method.

What gives?

Socket instance is created like this:

    SOCKET = io('', {
      path: `${VITE_WEBSOCKET_ENDPOINT}/socket.io/`,
      transports: ['websocket'],
      autoConnect: false,
    })

Then I call webSocketClient.connect() manually, later, when user has passed the auth.

Any clues?

[darrachequesne]

Hi! I was not able to reproduce the issue locally. Have you found the culprit?

[moltar]

No, did not find. I think it's a race condition. But I looked at the Socket.io code, and it is certainly handling on and onAny differently, at least it's in different places/classes.