Node.js worker threads are problematic, but they work great for us

Node.js's single-threaded model became a real problem for Inngest Connect when CPU-heavy user code starved the event loop, blocking WebSocket heartbeats and causing servers to drop workers as dead. The fix was moving connection internals into a worker thread — but Node's worker_threads model is fundamentally different from Go goroutines or Rust threads, requiring file-based entry points, serialized message passing, and careful bundler handling.