socket-io

Standardize Socket.IO event naming by enforcing a strict `type:subtype` convention with clear C→S and S→C directionality. Define typed event signatures and Zod schema validation in a shared package to ensure payload contracts match exactly between the server and web client.

The Socket.IO session lifecycle structure defines specific events for `session:launch`, `session:join`, `session:resume`, and `session:states` broadcasts. Each event requires consistent payload shapes, callback behaviors, and typed handler wiring to manage real-time session flows reliably.

Set up Socket.IO handlers by creating a repeatable directory structure for domain handlers and using DI-backed context. Apply Zod schema validation at handler entry to verify incoming payloads before processing real-time messaging events on both server and client sides.

Yes, the Socket.IO event contract pattern applies to existing TypeScript project structures by placing shared typed event definitions in a common package and mapping handler files to standard server and web context directories to match your current project patterns.

Validate the Socket.IO event sequence by running a targeted testing flow that confirms client requests trigger the expected server-to-client event broadcasts. This ensures the real-time messaging contract and handler wiring function correctly across the session lifecycle.

Mismatched Socket.IO payloads and handler errors usually stem from inconsistent event names, untyped signatures, and missing validation. Enforcing a shared typed event contract with Zod schema validation at handler entry resolves these integration bugs across client and server.