npm / @nestjs/bullmq

@nestjs/bullmq

What changed in @nestjs/bullmq 11 to 12, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-19.

6 breaking5 new APIs and options1 fixes and other

See which of these apply to your code, ranked, in your agent:

npx @unstale/cli init

@nestjs/bullmq 129 changes

Nest packages are ESM-only; CommonJS applications can continue consuming them through require(esm) on supported Node.js versions.
12.0.0upgrade guide
Lifecycle hooks are called by component hierarchy level, which can change execution order when providers or modules depend on one another.
12.0.0upgrade guide
Deep imports into build internals are no longer resolvable; import from the package root instead.
12.0.0release notes
Running a Nest 12 application requires Node.js v20.19+ or v22.12+ on the 22.x line.
12.0.0upgrade guide
Optional markers on constructor parameters are no longer inherited by subclasses; redeclare the marker in a subclass constructor to avoid UnknownDependenciesException.
12.0.0upgrade guide
CommonJS use requires Node 20.19+, 22.12+, or 24+, where require(esm) is enabled by default.
12.0.0release notes

The observability SDK adds opt-in instrumentation through the application instrument option, reporting jobs and queue consumers in Nest terms.
12.0.0upgrade guide
The package manifest is exposed as a subpath for tooling that resolves it through the package specifier.
12.0.0release notes

The exports map includes a require condition, so CommonJS Nest apps can continue using require('@nestjs/bullmq') with supported Node versions.
12.0.0release notes

Adds support for BullMQ v6.
11.0.5release notes
Adds the forceDisconnectOnShutdown option for graceful disconnection.
11.0.5release notes
Adds telemetry support for workers.
11.0.5release notes