Vantz Stockwell c72a280361 fix(api): WS gateways crashed on first forwarded event — WebSocket.OPEN undefined at runtime ...

Lesson 10 in the flesh: the onApplicationBootstrap fix made the NATS->
WS bridge actually deliver events for the first time, which instantly
crashed the API. esModuleInterop is off, so 'import WebSocket from ws'
compiles to ws_1.default = undefined; WebSocket.OPEN threw
'Cannot read properties of undefined' and killed the process on the
first heartbeat forward. All three WS guard sites (nats-bridge x2,
console gateway) switched to the import-agnostic instance constant
client.OPEN. Latent in every build — never hit because the bridge was
dead-on-boot until today.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-06-11 11:11:29 -04:00

..

src

fix(api): WS gateways crashed on first forwarded event — WebSocket.OPEN undefined at runtime

2026-06-11 11:11:29 -04:00

.gitignore

feat: Complete NestJS backend scaffold — 22 modules, 39 entities, WebSocket gateway

2026-02-15 21:29:25 -05:00

nest-cli.json

feat: Complete NestJS backend scaffold — 22 modules, 39 entities, WebSocket gateway

2026-02-15 21:29:25 -05:00

package-lock.json

fix: Replace socket.io with native WS adapter — fixes WebSocket 1006

2026-02-21 15:21:36 -05:00

package.json

fix: Replace socket.io with native WS adapter — fixes WebSocket 1006

2026-02-21 15:21:36 -05:00

tsconfig.build.json

feat: Complete NestJS backend scaffold — 22 modules, 39 entities, WebSocket gateway

2026-02-15 21:29:25 -05:00

tsconfig.json

feat: Complete NestJS backend scaffold — 22 modules, 39 entities, WebSocket gateway

2026-02-15 21:29:25 -05:00