Trigger.dev
Trigger.dev shipped observability and runtime communication primitives across three minor releases. The 4.4.0 wave added a SQL query engine (query.execute() with TRQL support for typed data access) and OTEL metrics collection from task workers (CPU, memory, event loop metrics, and custom metrics exported to ClickHouse with dashboard queryability). 4.4.2 introduced bidirectional input streams for tasks—developers define typed streams with streams.input<T>(), then suspend execution with .wait(), listen with .once(), or subscribe with .on(), while backends and React frontends send data via .send() and useInputStreamSend. 4.4.3 added Supabase environment variable syncing to pull database connection strings directly into Trigger.dev's env management, an errors page for self-hosted and cloud deployments, and fixed dev run cleanup by auto-canceling in-flight runs when the CLI exits.
Focused on real-time task communication and developer experience. Added input streams for bidirectional messaging with running tasks, letting you suspend execution with .wait(), consume messages with .once() or .on(), and send data from backends or React frontends. Also shipped automatic cleanup of dev runs when the CLI exits and a new Errors page for tracking issues across self-hosted and Cloud deployments.