socketio/socket.io-client

Issues

• Passing an empty object as ManagerOptions causes uri to be undefined.

  #1612 opened 2 months ago by tomlynchRNA
  2

• Getting Console Errors

  #1588 opened 2 months ago by mdahsanekram
  1

• Unable to resolve "@socket.io/component-emitter"

  #1598 opened 7 months ago by jpgorman
  5

• Debugging messages in Metro terminal with React Native

  #1578 opened 2 months ago by folin03
  1

• xhr poll error and websocket error on android react native when connecting

  #1558 opened 2 months ago by proohit
  11

• socket.on cannot accept generic "extends string" parameters

  #1571 opened 2 months ago by MHebes
  4

• error indicates a problem with Cross-Origin Resource Sharing (CORS) policy.

  #1579 opened 2 months ago by PixelJunkie33
  1

• React native ios crashes on production with extraHeaders

  #1593 opened 7 months ago by ouarrtaha
  4

• Next.js v14.0.0 server with socket.io client doesn't send messages with more than a few characters

  #1596 opened 2 months ago by njarraud
  5

• HI, there is a problem about socket.io-client 4.7.0 and netty-socketio 2.0.6. The auth parameter causes the socket connection to fail and returns parse error.

  #1604 opened 2 months ago by WilliamGrant
  3

• Encountering 'TransportError' with socket.io-client in React Native Production Mode

  #1602 opened 2 months ago by DDarkLexs
  1

• connection error

  #1605 opened 2 months ago by mehdish3022
  2

• socket.io-client not working on Android API 34 - iOS works normally (React Native)

  #1609 opened 2 months ago by mrbinhdrt
  2

• A parser error causes the socket connection to reconnect but the old connection is not closed

  #1611 opened 2 months ago by JoelBrenstrum
  1

• ESM build for 4.7.2 npm package generates with incorrect package version

  #1591 opened 3 months ago by bigcakes
  6

• Disabling reconnection while reconnecting isn't working

  #1610 opened 3 months ago by uncaught
  1

• v4.7.4 returns `No version specified and unable to automatically determine one` at runtime

  #1608 opened 3 months ago by yoav-melamed
  2

• [BUG] building socket.io-client@4.7.4 in a typescript based nodejs docker container results in type script error

  #1606 opened 4 months ago by PretoPlasma
  4

• Socket.io client keeps disconnecting and reconnecting at a fixed interval because of ping timeout

  #1584 opened a year ago by valentin-at-edlio
  19

• Socketio client keeps reconnecting after ping timeout, even after exhausting all reconnection attempts

  #1572 opened a year ago by Hackatosh
  1

• Minor: Event handler of 'offline' event must be added on the initial evaluation of worker script on Service Worker

  #1607 opened 4 months ago by wanfahmi11
  1

• Cannot build TS project when targeting Node16 or NodeNext

  #1589 opened 4 months ago by Julien-Marcou
  6

• Websocket Connection Becomes Unstable - Starts disconnecting and reconnecting after a while of being active

  #1603 opened 5 months ago by yakirs57
  3

• Won't switch to polling transport when Websocket transport failed

  #1599 opened 6 months ago by hassansin
  3

• Cannot listen to event dispared in useEffect() Next js 14.0.4

  #1601 opened 6 months ago by bbarchuk
  1

• Property 'of' does not exist on type 'Socket<DefaultEventsMap, DefaultEventsMap>'.

  #1600 opened 6 months ago by ciprianmacovei
  6

• Add an onMany method to attach a callback to multiple socket events.

  #1594 opened 7 months ago by zoosphar
  2

• [socket.io-client 2] Unable to run on webpack >= 5

  #1565 opened 7 months ago by giovanni-bertoncelli
  6

• Bug: `connect` event will not fire on browser client

  #1597 opened 7 months ago by KillerJulian
  6

• socket listen with AbortSignal

  #1592 opened 8 months ago by ZachHaber
  2

• more useful advice about namespace

  #1590 opened 9 months ago by 588q9
  0

• Stop using CommonJS or AMD dependencies

  #1586 opened a year ago by vitaly-t
  13

• errors from node-mudules

  #1582 opened a year ago by deepakchandrawanshi1063
  2

• Socket.on() functions can't read Jotai's atom variables

  #1577 opened a year ago by kaganAhmetOkan
  2

• How to properly disconnect from server in tests using jest.

  #1581 opened a year ago by GreatGaryCooper
  2

• Client faild to transport in other website

  #1583 opened a year ago by Ali-Aljufairi
  1

• The front-end has received the event, but does not trigger the handler.

  #1576 opened a year ago by Qyokizzzz
  2

• Add a best-practice example to use socket-io in React 18 with React.StrictMode

  #1575 opened a year ago by itayperry
  7

• After several reloads of the browser page, the message from the server not receiving

  #1573 opened a year ago by inagornyi
  2

• Infinite reconnect loop on parse error

  #1557 opened a year ago by MasterOdin
  1

• TypeScript build failing in Node.js-only environment

  #1561 opened a year ago by Jomshir98
  4

• Emitting an event with acknowledgement and timeout breaks the Typescript client-to-server event definitions

  #1555 opened 2 years ago by ltomov
  6

• New client does not always receive event that is emitted from 'connection'

  #1569 opened a year ago by WKampel
  1

• Socket.io-client fires "connect" event but can't send events to server

  #1567 opened a year ago by alexasparks
  0

• Websocket close was unclean : 1006

  #1566 opened 2 years ago by sumitk0110
  0

• socketInstance.timeout is not a function

  #1563 opened 2 years ago by nachogonzalezsibila
  2

• CVE-2022-2421 Insufficient validation when decoding a Socket.IO packet

  #1560 opened 2 years ago by 3XC1T3D
  2

• socket.emit does nothing. server accept connections and can recieve data, but cannot send event itself

  #1562 opened 2 years ago by fake364
  0

• handle "parse" errors

  #1554 opened 2 years ago by sebseb7
  2

• npm run build fails when socket-io-client library is imported in newly created react app

  #1553 opened 2 years ago by wickywaka
  3