chore(deps)(deps): Bump the nestjs group across 1 directory with 10 updates

[dependabot]

Bumps the nestjs group with 10 updates in the / directory:

Package	From	To
@nestjs/common	11.1.29	12.0.1
@nestjs/config	4.0.4	12.0.0
@nestjs/core	11.1.29	12.0.1
@nestjs/event-emitter	3.1.0	12.0.0
@nestjs/platform-express	11.1.29	12.0.1
@nestjs/platform-socket.io	11.1.29	12.0.1
@nestjs/websockets	11.1.29	12.0.1
@nestjs/cli	11.0.24	12.0.0
@nestjs/schematics	11.1.0	12.0.0
@nestjs/testing	11.1.29	12.0.1

Updates @nestjs/common from 11.1.29 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.29 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/platform-express from 11.1.29 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
• 043e951 fix(platform-express): address body parser review comments
• Additional commits viewable in compare view

Updates @nestjs/platform-socket.io from 11.1.29 to 12.0.1

Release notes

Sourced from @​nestjs/platform-socket.io'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
• 5ec2e58 Update io-adapter.ts
• e333721 Merge branch 'master' into platform-socket-types
• edb0034 Merge branch 'master' into v12.0.0
• 4535f43 chore(release): publish v11.2.1 release
• 5d1b19b Merge branch 'master' into v12.0.0
• f2a7e4b chore(release): publish v11.2.0 release
• 68dfc23 Merge branch 'master' into v12.0.0
• Additional commits viewable in compare view

Updates @nestjs/websockets from 11.1.29 to 12.0.1

Release notes

Sourced from @​nestjs/websockets'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
• 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
• 68dfc23 Merge branch 'master' into v12.0.0
• c470ddf Merge branch 'master' into v12.0.0
• Additional commits viewable in compare view

Updates @nestjs/cli from 11.0.24 to 12.0.0

Release notes

Sourced from @​nestjs/cli's releases.

Release 12.0.0

What's Changed

@nestjs/cli is now a native ES module, and the major version is aligned with the Nest 12 release line. Alongside the ESM move, the CLI no longer bundles webpack: every bundler-related package is an optional peer dependency now, so a default install is substantially smaller and you pull in only the builder you actually use. There are also two new commands — nest upgrade and nest deploy.

ESM migration

The package is published as pure ESM ("type": "module", compiled with NodeNext). All internal imports carry explicit .js extensions and the build output is ESM-only.

For the common case this is invisible — nest is a binary, and it keeps running your CJS and ESM projects alike. It matters if you import the CLI's internals programmatically (custom builders, plugin harnesses, scripts that drive @nestjs/cli/lib/...): those imports now resolve to ESM.

webpack is no longer a dependency

webpack, fork-ts-checker-webpack-plugin, tsconfig-paths-webpack-plugin, and webpack-node-externals moved from dependencies to optional peer dependencies, joining @swc/cli and @swc/core.

If you build with tsc (the default) or with SWC, nothing changes. If you use --builder webpack (or "webpack": true in nest-cli.json), install the bundler yourself:

npm i -D webpack webpack-node-externals fork-ts-checker-webpack-plugin tsconfig-paths-webpack-plugin

When a builder's peer dependency is missing, the CLI now reports the actual missing package name instead of surfacing the raw resolution error.

Rspack support

@rspack/core is supported as an optional peer dependency (^1.7.7 || ^2.1.10) and is the builder that nest new scaffolds into nest-cli.json for new projects.

• --builder rspack on nest build and nest start
• --rspackPath [path] to point at a custom Rspack config, mirroring --webpackPath
• Source maps are enabled in the Rspack defaults

New: nest upgrade

A new command (aliased nest update) that runs the upgrade schematic to migrate a Nest v11 project to v12 — dependency bumps, tsconfig and nest-cli.json migrations, and codemods for @nestjs/config, GraphQL, and NATS. See the @nestjs/schematics release notes for what the migration itself does.

nest upgrade

Options: -d, --dry-run, -s, --skip-install, -t, --tag [tag] (use a dist-tag such as next instead of the default version ranges), -c, --collection [name], and --observe / --no-observe to answer the @nestjs/observe prompt up front.

New: nest deploy

Deploy an application to the cloud, powered by Mau. Every option is forwarded verbatim to mau deploy, so the command claims no flags of its own.

nest deploy

Path confinement for build output

... (truncated)

Commits

• f4bcf48 chore(): release v12.0.0
• 6a24117 chore: resolve conflicts
• a05c24c chore: upgrade to v12
• a3ee7ba Merge pull request #3527 from nestjs/renovate/cimg-node-24.x
• 4f4f81f Merge pull request #3528 from nestjs/renovate/inquirer-prompts-8.x
• 1a07a85 fix(deps): update dependency @​inquirer/prompts to v8.7.0
• ede1547 chore(deps): update node.js to v24.20.0
• 82d99b3 chore(deps): update dependency @​rspack/core to v2.2.0 (#3525)
• 71859d0 chore(deps): update dependency oxlint to v1.80.0 (#3524)
• 3707956 test: fix flaky test in ci attempt nan +1
• Additional commits viewable in compare view

Install script changes

This version modifies prepare script that runs during installation. Review the package contents before updating.

Updates @nestjs/schematics from 11.1.0 to 12.0.0

Release notes

Sourced from @​nestjs/schematics's releases.

Release 12.0.0

What's Changed

@nestjs/schematics is now a native ES module, and the major version is aligned with the Nest 12 release line. Beyond the package itself going ESM, the bigger change is what it generates: nest new now scaffolds ESM applications by default, and a brand-new nest upgrade schematic migrates existing v11 projects to v12.

ESM migration

The package is published as pure ESM ("type": "module", compiled with NodeNext). All internal imports carry explicit .js extensions and the build output is ESM-only.

The package now requires Node.js >= 22.12.0 and declares a typescript >= 6.0.0 peer dependency. prettier ^3 remains an optional peer, used only when --format is passed.

require(esm) — CommonJS still works

You do not need to convert your tooling to ESM. Thanks to Node's require(esm) support, CommonJS consumers can still require('@nestjs/schematics') on the supported Node versions, so custom collections and CJS scripts that drive the schematics programmatically keep working unchanged.

nest new generates ESM by default

The application schematic gained a type option (esm | cjs) that defaults to esm:

Which module system would you like to use?
> ESM (ES Modules)         [ with vitest ]
  CJS (CommonJS)           [ with jest ]

• ESM projects get "type": "module", Vitest as the test runner (vitest.config.ts / vitest.config.e2e.ts), and "types": ["vitest/globals", "node"].
• CJS projects keep Jest, but the Jest configuration has moved out of package.json into a dedicated jest.config.ts.

Pass --type cjs (or answer the prompt) to keep the classic CommonJS layout.

Generated project defaults

• TypeScript 6, with module/moduleResolution set to nodenext, resolvePackageJsonExports: true, isolatedModules: true, and target: ES2023.
• oxlint replaces ESLint. New projects ship an oxlint.json and a "lint": "oxlint src/ test/" script instead of the ESLint config and its plugin chain.
• Rspack replaces webpack as the default builder in nest-cli.json.
• Nest dependencies are pinned to the v12 line (@nestjs/common, @nestjs/core, @nestjs/platform-express, @nestjs/testing).

ESM-aware generators

Every element generator (module, controller, service, resource, middleware, pipe, …) now detects whether the target project is ESM and appends .js to generated relative imports accordingly — including the imports it injects into an existing @Module() when wiring up a newly generated element. CJS projects are unaffected.

New: nest upgrade

A new schematic (aliased nest update) migrates a Nest v11 project to v12. It refuses to run on anything that isn't v11, then applies the migration in steps and prints a report of every change, every follow-up action, and every warning.

Dependencies — bumps all known @nestjs/* packages to ^12.0.0 (GraphQL packages to ^14.0.0), raises typescript to ^6.0.0 and engines.node to >=20.19.0, and reports any @nestjs/* package whose v12-compatible release it doesn't know about.

tsconfig — flags module: commonjs with legacy module resolution and any moduleResolution that TypeScript 6 dropped, and points out a missing rootDir in tsconfig.build.json (TS6 error TS5011).

@nestjs/config — moves library-specific validationOptions (Joi's allowUnknown, abortEarly, …) under validationOptions.libraryOptions, and raises joi to ^18 for its Standard Schema support.

... (truncated)

Commits

• 11d0160 chore(): release v12.0.0
• dca8524 Merge branch 'master' of https://github.com/nestjs/schematics
• 8ed3d58 chore: upgrade to v12
• f994553 chore(deps): update dependency oxlint to v1.80.0 (#2425)
• 5398976 fix: add missing root dir compiler option
• 46f07fd Merge pull request #2350 from nestjs/renovate/angular-cli-monorepo
• d01bb42 fix(upgrade): track upgrade.schema.d.ts
• f626d68 Merge branch 'v12.0.0' into master
• d5a0f5a feat(upgrade): add schematic to migrate v11 projects to v12
• e43d149 fix(deps): update angular-cli monorepo to v22.1.5
• Additional commits viewable in compare view

Updates @nestjs/testing from 11.1.29 to 12.0.1

Release notes

Sourced from @​nestjs/testing'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
• 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
• eb49dd1 test(testing): Add unit tests for @​nestjs/testing package
• 68dfc23 Merge branch 'master' into v12.0.0
• Additional commits viewable in compare view

[dependabot]

Labels

The following labels could not be found: dependencies. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
pulseticker	Ready	Preview	Sep 6, 2026 11:16pm UTC