Extend & integrate
Hook into the task lifecycle, watch what it does, and wire the Node.js SDK into the rest of your stack.
Hook into the task lifecycle, watch what it does, and wire the Node.js SDK into the rest of your stack.
Everything that attaches to flexiq from the outside: the extension points that run inside the task lifecycle, the signals they emit, and the frameworks and vendors on the other end of those signals.
Lifecycle events and middleware are the extension points for pushing any of these signals to an external system.
See what the queue is doing — counts, per-task latency, job progress, live
workers — and emit structured logs, all from the Queue handle with no extra
service.
Integrations are optional helpers that ship alongside the core SDK but are not
exported from the main @byteveda/flexiq barrel. Each lives behind its own
@byteveda/flexiq/contrib/* subpath and requires you to install its peer
dependency.
# Only install what you use.
pnpm add @opentelemetry/api # @byteveda/flexiq/contrib/otel
pnpm add prom-client # @byteveda/flexiq/contrib/prometheus
pnpm add @sentry/node # @byteveda/flexiq/contrib/sentry
pnpm add express # @byteveda/flexiq/contrib/express
pnpm add fastify # @byteveda/flexiq/contrib/fastify
pnpm add @nestjs/common reflect-metadata # @byteveda/flexiq/contrib/nestIntegrations never auto-initialize. Nothing runs until you call the export and register it with your queue or framework. If a peer dependency is missing, importing its subpath fails with a standard module-not-found error.