chore(deps): bump the production-dependencies group across 1 directory with 38 updates

[dependabot]

Bumps the production-dependencies group with 38 updates in the / directory:

Package	From	To
@alicloud/dysmsapi20170525	4.5.1	4.6.0
@nestjs/cache-manager	3.1.3	12.0.0
@nestjs/common	11.1.27	12.0.1
@nestjs/config	4.0.4	12.0.0
@nestjs/core	11.1.27	12.0.1
@nestjs/event-emitter	3.1.0	12.0.0
@nestjs/jwt	11.0.2	12.0.1
@nestjs/passport	11.0.5	12.0.0
@nestjs/platform-express	11.1.27	12.0.1
@nestjs/schedule	6.1.3	12.0.1
@nestjs/swagger	11.4.4	12.0.1
@nestjs/terminus	11.1.1	12.0.0
@prisma/adapter-pg	7.8.0	7.10.0
@sentry/node	10.68.0	10.73.0
archiver	7.0.1	8.0.0
class-validator	0.14.4	0.15.1
connect-redis	9.0.0	10.0.0
fast-xml-parser	5.9.3	5.11.1
http-proxy-middleware	3.0.7	4.2.0
ioredis	5.11.1	6.0.0
multer	2.2.0	2.3.0
nestjs-pino	4.6.1	5.1.0
nodemailer	7.0.13	10.0.0
prisma	7.8.0	7.10.0
redis	5.12.1	6.2.1
@prisma/client	7.8.0	7.10.0
@hookform/resolvers	5.4.0	5.9.1
@sentry/react	10.68.0	10.73.0
@tanstack/react-query	5.101.2	5.102.8
axios	1.18.1	1.20.0
lucide-react	0.556.0	1.41.0
react-day-picker	9.14.0	10.0.1
react-hook-form	7.80.0	7.87.0
recharts	3.9.0	3.10.1
zod	4.4.3	4.5.4
@varlet/touch-emulator	2.22.8	3.20.6
@vueuse/core	10.11.1	14.4.0
pinia	3.0.4	4.0.3

Updates @alicloud/dysmsapi20170525 from 4.5.1 to 4.6.0

Updates @nestjs/cache-manager from 3.1.3 to 12.0.0

Release notes

Sourced from @​nestjs/cache-manager's releases.

Release 12.0.0

What's Changed

@nestjs/cache-manager is now a native ES module, and the major version is aligned with the Nest 12 release line (there is no 4.x — 3.1.3 goes straight to 12.0.0).

ESM migration

The package is published as pure ESM ("type": "module", compiled with NodeNext) behind a proper exports map. The legacy root index.js / index.d.ts / index.ts shims are gone, and deep imports into build internals are no longer resolvable — import from the package root:

import { CacheModule, CacheInterceptor, CacheKey, CacheTTL } from '@nestjs/cache-manager';

require(esm) — CommonJS still works

You do not need to convert your app to ESM. Thanks to Node's require(esm) support, CommonJS consumers can keep using require('@nestjs/cache-manager') unchanged — the exports map points both import and require at the same ESM build, and Node loads it natively.

This is why the supported Node range is now enforced via engines:

"engines": {
  "node": "^20.19.0 || ^22.12.0 || >=24.0.0"
}

Those are the Node versions where require(esm) is available unflagged. On older Node versions, requiring this package from CommonJS will fail with ERR_REQUIRE_ESM.

Upgrading

npm i @nestjs/cache-manager@12

Checklist:

• Ensure you're on Node ^20.19.0, ^22.12.0, or >=24.0.0.
• Replace any deep imports (e.g. @nestjs/cache-manager/dist/...) with root imports.
• No changes needed to CacheModule.register() / registerAsync(), interceptors, or decorators.

Commits

• 661bc00 chore(): release v12.0.0
• 085ae1a chore: upgrade to v12
• 3a07e0b chore(deps): update dependency oxlint to v1.80.0 (#1152)
• 5f1ad64 chore(deps): update nest monorepo to v11.2.3 (#1151)
• f34fe5a chore(deps): update dependency vite to v8.2.2 (#1150)
• 288ea83 Merge pull request #1149 from miso-kyoungminkim/cachettl-ms-comment
• 9c08ea6 chore(deps): update dependency oxlint to v1.79.0 (#1148)
• f2b60ee docs(cache-ttl): clarify that ttl is in milliseconds
• f12d697 chore(deps): update dependency vitest to v4.1.11 (#1147)
• d0030ab Merge pull request #1067 from nestjs/chore/esm-migration
• Additional commits viewable in compare view

Updates @nestjs/common from 11.1.27 to 12.0.1

Release notes

Sourced from @​nestjs/common's releases.

v12.0.0

NestJS v12.0.0

NestJS 12 is centered around ESM-ready packages, first-class Standard Schema support for validation and serialization, a rebuilt CLI, and native observability through the new @nestjs/observe SDK.

Existing CommonJS applications keep working — migrating your own code to ESM is entirely optional.

📖 Full migration guide

---

Upgrading

Upgrade the CLI first, since the upgrade command ships with it:

npm i -g @nestjs/cli@latest

Then, from the root of your project:

nest upgrade

nest upgrade moves every @nestjs/* package to its v12-compatible major at once and applies the mechanical parts of the migration for you — nest-cli.json webpack options, the GraphQL playground → graphiql rename and subscriptions transport swap, the NATS package replacement, @nestjs/config validation options, Jest and Joi bumps — then prints a report of everything it changed and everything you still need to review by hand. Run it with --dry-run first to see that report without touching your files.

It deliberately does not migrate your project to ESM, Vitest, or oxlint. Those are the defaults for newly generated projects; existing projects adopt them on their own schedule.

Node.js: v12 requires Node.js v20.19+ or v22.12+. Both require(esm) and the ESM packages depend on it; the upgrade command refuses to run on older releases (including the 21.x line). The latest active LTS is recommended.

---

Highlights

ESM packages

All core Nest packages now ship as ESM. Thanks to require(esm) in modern Node.js, most existing CommonJS applications continue to work without a rewrite. Review custom bootstrapping scripts, build tooling, and test runners if they assume CommonJS-only packages.

nest new now asks whether to scaffold a CommonJS or an ESM project.

Standard Schema validation

Route parameter decorators — @Body(), @Query(), @Param(), @RawBody() — accept a new schema option, designed for Standard Schema compatible libraries such as Zod, Valibot, and ArkType:

@Post()
create(@Body({ schema: createUserSchema }) body: CreateUserDto) {
  return this.usersService.create(body);
}
</tr></table> 

... (truncated)

Commits

• 4c751c5 chore(release): publish v12.0.1 release
• 6494a6c chore(release): publish v12.0.0 release
• e306724 fix(deps): update dependency file-type to v22
• edb0034 Merge branch 'master' into v12.0.0
• 4535f43 chore(release): publish v11.2.1 release
• e255755 chore: resolve conflicts, minor fixes
• 5d1b19b Merge branch 'master' into v12.0.0
• f2a7e4b chore(release): publish v11.2.0 release
• b2e7fb5 Merge pull request #17469 from nestjs/feat/sse-signal
• 6498f11 feat: signal should finalize in every case
• Additional commits viewable in compare view

Updates @nestjs/config from 4.0.4 to 12.0.0

Release notes

Sourced from @​nestjs/config's releases.

12.0.0

What's Changed

@nestjs/config is now a native ES module, environment validation is built on Standard Schema instead of Joi-specific code, and the major version is aligned with the Nest 12 release line (there is no 5.x — 4.0.4 goes straight to 12.0.0).

ESM migration

The package is published as pure ESM ("type": "module", compiled with NodeNext) behind a proper exports map. The legacy root index.js / index.d.ts shims are gone, and deep imports into build internals are no longer resolvable — import from the package root.

// ✅
import { ConfigModule, ConfigService } from '@nestjs/config';
// ❌ no longer resolvable
import { ConfigService } from '@​nestjs/config/dist/config.service';

require(esm) — CommonJS still works

You do not need to convert your app to ESM. Thanks to Node's require(esm) support (Node 20.19+ / 22.12+), a CommonJS app can keep using require('@nestjs/config') unchanged.

Validation is now Standard Schema based

validationSchema accepts any schema implementing the Standard Schema spec — Zod (v3, v4, v4-mini), Valibot, ArkType, Joi 18+, and anything else that adopts it. There is no longer any Joi-specific code path in the module, and Joi is no longer implied as the validation library.

ConfigModule.forRoot({
  validationSchema: z.object({
    PORT: z.coerce.number().default(3000),
    DATABASE_NAME: z.string(),
  }),
});

Joi keeps working — it implements Standard Schema as of v18 — and the historical abortEarly: false / allowUnknown: true defaults are still applied automatically for Joi schemas, so existing Joi setups behave as before.

Breaking: validationOptions shape

Options are now the Standard Schema Options object, and library-specific settings move under libraryOptions:

// Before (4.x)
validationOptions: { allowUnknown: false, abortEarly: true }
// Now (12.x)
validationOptions: { libraryOptions: { allowUnknown: false, abortEarly: true } }

The generic parameter changed accordingly: ConfigModuleOptions<ValidationOptions extends StandardSchemaV1.Options>, and validationSchema is typed as StandardSchemaV1 rather than any — a schema that does not implement the spec is now a compile-time error instead of a runtime one.

... (truncated)

Commits

• 269312f chore(): release v12.0.0
• 5748c1f chore: upgrade to v12
• d833a6a chore(deps): update dependency oxlint to v1.80.0 (#2408)
• 4555cbc chore(deps): update nest monorepo to v11.2.3 (#2407)
• 4561739 chore(deps): update dependency vite to v8.2.2 (#2406)
• 0fc13bb chore(deps): update dependency joi to v18.2.5 (#2405)
• 22642b8 chore(deps): update dependency oxlint to v1.79.0 (#2404)
• d3a7dd5 chore(deps): update dependency vitest to v4.1.11 (#2403)
• 8c87973 chore(deps): update dependency zod to v4.4.3 (#2402)
• 949dc88 Merge pull request #2356 from nestjs/renovate/cimg-node-24.x
• Additional commits viewable in compare view

Updates @nestjs/core from 11.1.27 to 12.0.1

Release notes

Sourced from @​nestjs/core's releases.

v12.0.0

NestJS v12.0.0

NestJS 12 is centered around ESM-ready packages, first-class Standard Schema support for validation and serialization, a rebuilt CLI, and native observability through the new @nestjs/observe SDK.

Existing CommonJS applications keep working — migrating your own code to ESM is entirely optional.

📖 Full migration guide

---

Upgrading

Upgrade the CLI first, since the upgrade command ships with it:

npm i -g @nestjs/cli@latest

Then, from the root of your project:

nest upgrade

nest upgrade moves every @nestjs/* package to its v12-compatible major at once and applies the mechanical parts of the migration for you — nest-cli.json webpack options, the GraphQL playground → graphiql rename and subscriptions transport swap, the NATS package replacement, @nestjs/config validation options, Jest and Joi bumps — then prints a report of everything it changed and everything you still need to review by hand. Run it with --dry-run first to see that report without touching your files.

It deliberately does not migrate your project to ESM, Vitest, or oxlint. Those are the defaults for newly generated projects; existing projects adopt them on their own schedule.

Node.js: v12 requires Node.js v20.19+ or v22.12+. Both require(esm) and the ESM packages depend on it; the upgrade command refuses to run on older releases (including the 21.x line). The latest active LTS is recommended.

---

Highlights

ESM packages

All core Nest packages now ship as ESM. Thanks to require(esm) in modern Node.js, most existing CommonJS applications continue to work without a rewrite. Review custom bootstrapping scripts, build tooling, and test runners if they assume CommonJS-only packages.

nest new now asks whether to scaffold a CommonJS or an ESM project.

Standard Schema validation

Route parameter decorators — @Body(), @Query(), @Param(), @RawBody() — accept a new schema option, designed for Standard Schema compatible libraries such as Zod, Valibot, and ArkType:

@Post()
create(@Body({ schema: createUserSchema }) body: CreateUserDto) {
  return this.usersService.create(body);
}
</tr></table> 

... (truncated)

Commits

• 4c751c5 chore(release): publish v12.0.1 release
• 3c25112 chore: update peer deps
• 6494a6c chore(release): publish v12.0.0 release
• c9d59f2 chore: expose missing internals
• 45485b5 fix(core): circular durable providers issue #17562
• f94e9eb fix(core): preserve middleware arity and harden instance decorator
• 1dcbc25 fix(core): instrument midldeware issue #17554
• f5bf4dd docs(core): update Mercure SSE header comment to current path
• edb0034 Merge branch 'master' into v12.0.0
• 4535f43 chore(release): publish v11.2.1 release
• Additional commits viewable in compare view

Updates @nestjs/event-emitter from 3.1.0 to 12.0.0

Release notes

Sourced from @​nestjs/event-emitter's releases.

Release 12.0.0

What's Changed

@nestjs/event-emitter is now a native ES module, and the major version is aligned with the Nest 12 release line (there is no 4.x — 3.1.0 goes straight to 12.0.0).

ESM migration

The package is published as pure ESM ("type": "module", compiled with NodeNext) behind a proper exports map. Deep imports into build internals (@nestjs/event-emitter/dist/...) are no longer resolvable — import from the package root.

// still the only supported entry point
import { EventEmitterModule, OnEvent } from '@nestjs/event-emitter';

require(esm) — CommonJS still works

You do not need to convert your app to ESM. Thanks to Node's require(esm) support, a plain CommonJS Nest app can keep doing:

const { EventEmitterModule, OnEvent } = require('@nestjs/event-emitter');

Both load paths are covered by a smoke test that runs against the built package in CI, so an interop regression fails the build rather than reaching npm.

Node.js requirement

engines.node is now >=20.19.0. That is the first Node 20 release with unflagged require(esm) (Node 22.12+ on the 22 line). On older runtimes a CommonJS app cannot require() this package at all.

Importing EventEmitter2

eventemitter2 is a CommonJS package, so under ESM Node cannot statically detect its named exports and import { EventEmitter2 } from 'eventemitter2' throws at load time. This package re-exports the class off the default export for you — import it from here instead:

import { EventEmitter2 } from '@nestjs/event-emitter';

It is still exported as both a value and a type, so existing type annotations keep working.

Newly exported from the package root

• EVENT_LISTENER_METADATA — the metadata key @OnEvent writes, so custom decorators can produce listener metadata the loader understands
• the public interfaces (EventEmitterModuleOptions, OnEventOptions, EventPayloadHost), which previously had to be reached through a deep import

Commits

• e37ba08 chore(): release v12.0.0
• f203a1b chore: upgrade to v12
• 906133a chore(deps): update nest monorepo to v11.2.3 (#1806)
• 71948fd chore(deps): update dependency oxlint to v1.80.0 (#1805)
• 2d43ede chore(deps): update dependency vite to v8.2.2 (#1804)
• 3803013 chore(deps): update dependency oxlint to v1.79.0 (#1803)
• c5d49a5 chore(deps): update dependency vitest to v4.1.11 (#1802)
• c4b5e86 Merge pull request #1740 from nestjs/renovate/cimg-node-24.x
• 227d204 Merge pull request #1718 from nestjs/chore/esm-migration
• 83a3b36 fix: make esm build loadable and guard it in ci
• Additional commits viewable in compare view

Updates @nestjs/jwt from 11.0.2 to 12.0.1

Release notes

Sourced from @​nestjs/jwt's releases.

Release 12.0.1

• fix: jsonwebtoken esm imports (05d0075)

Release 12.0.0

What's Changed

@nestjs/jwt is now a native ES module, and the major version is aligned with the Nest 12 release line

ESM migration

The package is published as pure ESM ("type": "module", compiled with NodeNext) behind a proper exports map. The legacy root index.js / index.d.ts / index.ts shims are gone, and deep imports into build internals are no longer resolvable — import from the package root.

// ✅
import { JwtModule, JwtService } from '@nestjs/jwt';
// ❌ no longer resolvable
import { JwtService } from '@​nestjs/jwt/dist/jwt.service';

require(esm) — CommonJS still works

You do not need to convert your app to ESM. Thanks to Node's require(esm) support (Node 20.19+, 22.12+, and all of 24.x), a CommonJS Nest application can keep requiring the package exactly as before:

const { JwtModule, JwtService } = require('@nestjs/jwt');

TypeScript users compiling to CommonJS are unaffected as long as their runtime is on a supported Node version. On older Node releases, require() of this package will throw ERR_REQUIRE_ESM — upgrade Node, or switch the consuming code to import.

jsonwebtoken re-exports

The error classes re-exported from jsonwebtoken (TokenExpiredError, NotBeforeError, JsonWebTokenError) are now re-exported explicitly by name instead of via a star export, so they resolve correctly under ESM interop with the CJS jsonwebtoken package. No import changes are needed on your side:

import { TokenExpiredError } from '@nestjs/jwt';

Upgrading

npm install @nestjs/jwt@12

For most applications this is a drop-in upgrade. Action is only required if you were relying on deep imports into dist/, or are running a Node version older than 20.19 with a CommonJS app.

Commits

• 6c75fa6 chore(): release v12.0.1
• 05d0075 fix: jsonwebtoken esm imports
• 8853ee8 chore(): release v12.0.0
• b8455f2 chore: upgrade to v12
• 542e29e chore(deps): update dependency oxlint to v1.80.0 (#2260)
• ae0d0d7 chore(deps): update nest monorepo to v11.2.3 (#2259)
• af3ad43 chore(deps): update dependency oxlint to v1.79.0 (#2258)
• 53c8fee chore(deps): update dependency vitest to v4.1.11 (#2257)
• 7014c3a Merge pull request #2205 from nestjs/renovate/cimg-node-24.x
• 54a4c5c Merge pull request #2186 from nestjs/chore/esm-migration
• Additional commits viewable in compare view

Updates @nestjs/passport from 11.0.5 to 12.0.0

Release notes

Sourced from @​nestjs/passport's releases.

Release 12.0.0

What's Changed

@nestjs/passport is now a native ES module, and the major version is aligned with the Nest 12 release line.

ESM migration

The package is published as pure ESM ("type": "module", compiled with NodeNext) behind a proper exports map. The legacy root index.js / index.d.ts / index.ts shims are gone, and deep imports into build internals (e.g. @nestjs/passport/dist/auth.guard) are no longer resolvable — import from the package root:

import { AuthGuard, PassportModule, PassportStrategy } from '@nestjs/passport';

require(esm) — CommonJS still works

You do not need to convert your app to ESM. Thanks to Node's require(esm) support, a CommonJS app can keep doing:

const { AuthGuard, PassportModule } = require('@nestjs/passport');

This requires Node.js 20.19+ or 22.12+ (where require(esm) is enabled by default). On older Node versions you must either upgrade Node or move your app to ESM.

AuthGuard no longer forwards module options to passport.authenticate()

defaultStrategy and property — options that belong to PassportModule.register(), not to Passport itself — were being passed straight through to passport.authenticate(), where they could collide with strategy-level options. They are now stripped before the call, so a strategy only ever receives real AuthenticateOptions.

The signature of getAuthenticateOptions() changed accordingly:

// before
getAuthenticateOptions(
  context: ExecutionContext,
): Promise<IAuthModuleOptions> | IAuthModuleOptions | undefined;
// after
getAuthenticateOptions(
context: ExecutionContext,
):
| Promise<AuthGuardAuthenticateOptions>
| AuthGuardAuthenticateOptions
| undefined;

AuthGuardAuthenticateOptions is exported from the package root and is passport.AuthenticateOptions with defaultStrategy explicitly disallowed. If you override getAuthenticateOptions() and return defaultStrategy, TypeScript will now flag it — remove it and set it via PassportModule.register({ defaultStrategy: '...' }) instead.

Peer dependencies

"peerDependencies": {
</tr></table> 

... (truncated)

Commits

• 0f15350 chore(): release v12.0.0
• c6af6f6 chore: upgrade to v12
• d05c93e chore(deps): update dependency oxlint to v1.80.0 (#2309)
• 8d06e0c chore(deps): update nest monorepo to v11.2.3 (#2308)
• 875fddc chore(deps): update dependency oxlint to v1.79.0 (#2307)
• dd63061 chore(deps): update vitest monorepo to v4.1.11 (#2306)
• 28e6701 Merge pull request #2300 from GiHoon1123/fix-947-authenticate-options
• 849d11c Merge master into fix-947-authenticate-options, resolve conflicts
• de02b20 Merge pull request #2250 from nestjs/renovate/cimg-node-24.x
• e27a9c8 Merge pull request #2230 from nestjs/chore/esm-migration
• Additional commits viewable in compare view

Updates @nestjs/platform-express from 11.1.27 to 12.0.1

Release notes

Sourced from @​nestjs/platform-express's releases.

v12.0.0

NestJS v12.0.0

NestJS 12 is centered around ESM-ready packages, first-class Standard Schema support for validation and serialization, a rebuilt CLI, and native observability through the new @nestjs/observe SDK.

Existing CommonJS applications keep working — migrating your own code to ESM is entirely optional.

📖 Full migration guide

---

Upgrading

Upgrade the CLI first, since the upgrade command ships with it:

npm i -g @nestjs/cli@latest

Then, from the root of your project:

nest upgrade

nest upgrade moves every @nestjs/* package to its v12-compatible major at once and applies the mechanical parts of the migration for you — nest-cli.json webpack options, the GraphQL playground → graphiql rename and subscriptions transport swap, the NATS package replacement, @nestjs/config validation options, Jest and Joi bumps — then prints a report of everything it changed and everything you still need to review by hand. Run it with --dry-run first to see that report without touching your files.

It deliberately does not migrate your project to ESM, Vitest, or oxlint. Those are the defaults for newly generated projects; existing projects adopt them on their own schedule.

Node.js: v12 requires Node.js v20.19+ or v22.12+. Both require(esm) and the ESM packages depend on it; the upgrade command refuses to run on older releases (including the 21.x line). The latest active LTS is recommended.

---

Highlights

ESM packages

All core Nest packages now ship as ESM. Thanks to require(esm) in modern Node.js, most existing CommonJS applications continue to work without a rewrite. Review custom bootstrapping scripts, build tooling, and test runners if they assume CommonJS-only packages.

nest new now asks whether to scaffold a CommonJS or an ESM project.

Standard Schema validation

Route parameter decorators — @Body(), @Query(), @Param(), @RawBody() — accept a new schema option, designed for Standard Schema compatible libraries such as Zod, Valibot, and ArkType:

@Post()
create(@Body({ schema: createUserSchema }) body: CreateUserDto) {
  return this.usersService.create(body);
}
</tr></table> 

... (truncated)

Commits

• 4c751c5 chore(release): publish v12.0.1 release
• 3c25112 chore: update peer deps
• 6494a6c chore(release): publish v12.0.0 release
• e03cf5c fix(express,fastify): apply falsy status codes in reply()
• edb0034 Merge branch 'master' into v12.0.0
• 4535f43 chore(release): publish v11.2.1 release
• e255755 chore: resolve conflicts, minor fixes
• 5d1b19b Merge branch 'master' into v12.0.0
• f2a7e4b chore(release): publish v11.2.0 release
• 03587a1 chore(release): publish v11.1.29 release
• Additional commits viewable in compare view

Updates @nestjs/schedule from 6.1.3 to 12.0.1

Release notes

Sourced from @​nestjs/schedule's releases.

Release 12.0.1

What's Changed

• feat: export ScheduleExplorer from the package entry point by @​kamilmysliwiec in nestjs/schedule#2349

Full Changelog: nestjs/schedule@12.0.0...12.0.1

Release 12.0.0

What's Changed

@nestjs/schedule is now a native ES module, and the major version is aligned with the Nest 12 release line (there is no 7.x — 6.1.3 goes straight to 12.0.0).

ESM migration

The package is published as pure ESM ("type": "module", compiled with NodeNext) behind a proper exports map. The legacy root index.js / index.d.ts / index.ts shims are gone, and deep imports into build internals are no longer resolvable — import from the package root.

// ✅
import { ScheduleModule, Cron, CronExpression } from '@nestjs/schedule';
// ❌ no longer resolvable
import { CronExpression } from '@​nestjs/schedule/dist/enums/cron-expression.enum';

Only . and ./package.json are exported.

require(esm) — CommonJS still works

You do not need to convert your app to ESM. Thanks to Node's require(esm) support, a CommonJS app can keep doing:

const { ScheduleModule } = require('@nestjs/schedule');

This is why the package now declares "engines": { "node": ">=20.19.0" } — require(esm) is unflagged from Node 20.19 / 22.12 onward. On older Node versions the require will throw ERR_REQUIRE_ESM.

Fixes

• Duplicate scheduler names are now rejected at startup. Two @Cron, @Interval, or @Timeout declarations sharing an explicit name previously slipped past decorator collection and only conflicted later; the DUPLICATE_SCHEDULER error is now thrown during initialization, where you can actually see it.

Upgrading

npm i @nestjs/schedule@12

• Node 20.19+ (or 22.12+) is required.
• Replace any deep imports with root imports.
• If you were importing from the removed root index.js shim path explicitly, drop the path — @nestjs/schedule resolves on its own.

Commits

• 1df146c chore(): release v12.0.1
• 7c241a5 Merge pull request #2349 from nestjs/feat/export-schedule-explorer
• 00d3db8 feat: export ScheduleExplorer from the package entry point
• 55e94dd Merge pull request #2347 from nestjs/renovate/cimg-node-24.x
• 7e5d551 Merge pull request #2348 from nestjs/renovate/nest-monorepo
• 5237ab0 chore(deps): update nest monorepo to v12.0.1
• 6bd6e14 chore(): release v12.0.0
• 6719285 feat: support nestjs v12
• 3bcca07 chore(deps): update node.js to v24.20.0
• 1b24bb7 chore(deps): update nest monorepo to v11.2.3 (#2346)
• Additional commits viewable in compare view

Updates @nestjs/swagger from 11.4.4 to 12.0.1

Release notes

Sourced from @​nestjs/swagger's releases.

Release 12.0.1

12.0.1 (2026-08-28)

Bug fixes

• #4082 fix: esm hoist static imports (@​kamilmysliwiec)

Dependencies

• #4077 chore(deps): update dependency swagger-ui-dist to v5.32.14 (@​renovate[bot])

Committers: 1

• Kamil Mysliwiec (@​kamilmysliwiec)

Release 12.0.0

What's Changed

@nestjs/swagger is now a native ES module, requires Nest 12, and changes how nullable schemas are spelled in the generated document.

ESM migration

The package is published as pure ESM ("type": "module", compiled with NodeNext) behind a proper exports map. The legacy root index.ts / plugin.js / plugin.ts shims are gone, and deep imports into build internals are no longer resolvable — import from the package root (@nestjs/swagger) or from @nestjs/swagger/plugin.

require(esm) — CommonJS still works

You do not need to convert your app to ESM. Thanks to Node's require(esm) support, a CommonJS app can keep doing const { SwaggerModule } = require('@nestjs/swagger'). The CLI plugin entry (@nestjs/swagger/plugin) also keeps a require condition so nest-cli.json setups load it unchanged.

This is why the package now declares "engines": { "node": "^20.19.0 || >=22.12.0" } — those are the Node versions where require(esm) is available without a flag.

Nest 12 peer dependencies

@nestjs/common and @nestjs/core peers are now ^12.0.0. @nestjs/mapped-types moves to 12.0.0 (itself ESM, with its major aligned to the Nest 12 line), so PartialType, PickType, OmitType and IntersectionType come from an ESM build too.

Standard Schema support

Schemas passed to Nest 12's route decorators (for example @Body({ schema: z.object({ ... }) })) can now be reflected into the OpenAPI document. Supply an adapter via the new standardSchemaConverter document option:

import { SwaggerModule, DocumentBuilder } from '@nestjs/swagger';
import type { SwaggerDocumentOptions } from '@nestjs/swagger';
import { createSchema } from 'zod-openapi';
import type { ZodType } from 'zod';
// Standard Schema exposes the producing library under ~standard.vendor,
// which is how you narrow the raw value to a library-specific type.
function isZodSchema(schema: unknown): schema is ZodType {
return (
!!schema &&
typeof schema === 'object' &&
(schema as { '~standard'?: { vendor?: string } })['~standard']?.vendor ===
'zod'
);
</tr></table>

... (truncated)

Commits

• 4274e7c chore(): release v12.0.1
• 325d009 Merge pull request #4082 from nestjs/fix/esm-hoist-static-imports
• 8980a54 fix: esm hoist static imports
• 31b0bf4 chore(deps): update dependency lint-staged to v17.4.1 (#4078)
• b71a812 Merge pull request #4077 from nestjs/renovate/swagger-ui-dist-5.x-lockfile
• ec18a13 chore(deps): update dependency swagger-ui-dist to v5.32.14
• 0f85b4c Merge pull request #4072 from nestjs/renovate/js-yaml-5.x
• 7d8b38e Merge pull request #4076 from nestjs/renovate/vite-8.x-lockfile
• ebc4cb8 Merge pull request #4069 from nestjs/renovate/zod-openapi-6.x
• 71e1769 Merge pull request #4068 from nestjs/renovate/swagger-ui-dist-5.x
• Additional commits viewable in compare view

Updates @nestjs/terminus from 11.1.1 to 12.0.0

Release notes

Sourced from @​nestjs/terminus's releases.

Release 12.0.0

12.0.0 (2026-08-31)

Bug Fixes

• close the microservice client when the ping fails (8826bc6)
• http: create a dedicated HttpService instead of resolving from DI (163bfef), closes #2667
• microservice: stop RMQ pingCheck from asserting a queue per probe (9afc532), closes #2680
• mongoose: ping the database instead of checking readyState (e1c6486), closes #2661
• set shutting_down before awaiting the graceful shutdown timeout (1615c29)

Features

• ship the package as ESM (fae6663)
• add attempt() function (ef9ab99)
• add degraded status for health indicator (1cfb8af)
• add responseTime to the HealthCheckResult (a0434ae)
• @nestjs/terminus no longer has runtime dependencies

BREAKING CHANGES

• the package is now ESM-only and requires Node ^20.19.0 || ^22.12.0 || >=24.0.0.
• the deprecated HealthIndicator base class and its getStatus() have been removed. Migrate custom indicators to HealthIndicatorService: super.getStatus(key, isHealthy, data) becomes this.healthIndicatorService.check(key).up(data) / .down(data).
• the deprecated error classes are no longer exported: HealthCheckError, ConnectionNotFoundError, TimeoutError, StorageExceededError, UnhealthyResponseCodeError, MongoConnectionError.
• throwing inside a health indicator no longer produces a 503. In v11, a thrown HealthCheckError was unwrapped into the health check result; now any thrown error is treated as an unexpected failure (500) and only a returned down result marks the check unhealthy (503).

Release 12.0.0-next.1

12.0.0-next.1 (2026-08-31)

Features

• add .cacheFor() builder (ba59644)
• add degraded status for health indicator (1cfb8af)
• add responseTime to the HealthCheckResponse (a0434ae)

Release 12.0.0-next.0

12.0.0-next.0 (2026-08-30)

Bug Fixes

... (truncated)

Changelog

Sourced from @​nestjs/terminus's changelog.

12.0.0 (2026-08-31)

12.0.0-next.1 (2026-08-31)

Features

• add .cacheFor() builder (ba59644)
• add degraded status for health indicator (1cfb8af)
• add responseTime to the HealthCheckResponse (a0434ae)

12.0.0-next.0 (2026-08-30)

Bug Fixes

• close the microservice client when the ping fails (8826bc6)
• http: create a dedicated HttpService instead of resolving from DI (163bfef), closes #2667
• microservice: stop RMQ pingCheck from asserting a queue per probe (9afc532), closes #2680
• mongoose: ping the database instead of checking readyState (e1c6486), closes #2661
• set shutting_down before awaiting the graceful shutdown timeout (1615c29)

Features

• add attempt() function (ef9ab99)
• Ship the package as ESM (fae6663)

BREAKING CHANGES

• the package is now ESM-only and requires Node ^20.19.0 || ^22.12.0 || >=24.0.0.

11.1.0 (2026-02-17)

Bug Fixes

• deps: update dependency @​grpc/grpc-js to v1.12.6 (7dd0d5f)
• deps: update dependency @​mikro-orm/nestjs to v6.1.0 (177fc8c)
• deps: update dependency @​mikro-orm/nestjs to v6.1.1 (8e3b253)
• deps: update dependency @​nestjs/mongoose to v11.0.1 (0af02b5)
• deps: update dependency @​nestjs/typeorm to v11 (687a4fe)
• deps: update dependency ioredis to v5.4.2 (47125b6)
• deps: update dependency mongoose to v8.10.1 (4b8e133)
• deps: update dependency mysql2 to v3.12.0 (0970ecd)
• deps: update dependency rxjs to v7.8.2 (4cceadb)
• deps: update dependency typeorm to v0.3.22 (b0e6662)
• deps: update mikro-orm monorepo to v6.4.5 (5ece0f8)

... (truncated)

Commits

• 940cb35 chore(): release v12.0.0
• b7a086e Merge pull request

[dependabot]

Looks like these dependencies are updatable in another way, so this is no longer needed.