Disabling Socket.io transport in FeathersJS v5: handling unexpected client connections
When building a low‑traffic FeathersJS v5 application, developers often disable the Socket.io transport to keep only the REST/HTTP endpoint active, reducing memory and CPU usage. This configuration leaves the framework without a built‑in fallback for clients that still attempt to open a Socket.io connection. The absence of a documented automatic fallback to
socketio