chore(deps): bump the nest group with 9 updates

[dependabot]

Bumps the nest group with 9 updates:

Package	From	To
@nestjs/apollo	13.4.0	14.0.0
@nestjs/common	11.1.19	12.0.1
@nestjs/config	4.0.4	12.0.0
@nestjs/core	11.1.19	12.0.1
@nestjs/graphql	13.4.0	14.0.0
@nestjs/platform-express	11.1.19	12.0.1
@nestjs/typeorm	11.0.1	12.0.1
@nestjs/schematics	11.1.0	12.0.0
@nestjs/testing	11.1.19	12.0.1

Updates @nestjs/apollo from 13.4.0 to 14.0.0

Release notes

Sourced from @​nestjs/apollo's releases.

v14.0.0

What's Changed

@nestjs/graphql, @nestjs/apollo and @nestjs/mercurius are now native ES modules, and this major targets the Nest 12 release line.

ESM migration

All three packages are published as pure ESM ("type": "module", compiled with NodeNext) behind a proper exports map. Deep imports into build internals are no longer resolvable — import from the package root:

// ❌ no longer resolvable
import { GraphQLModule } from '@nestjs/graphql/dist/graphql.module';
// ✅
import { GraphQLModule } from '@​nestjs/graphql';

The one deep entry point that remains public is the CLI plugin:

// ✅ still supported
import { before } from '@nestjs/graphql/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 Nest app can keep require()-ing these packages unchanged. The @nestjs/graphql/plugin entry additionally ships a CJS shim (plugin.cjs), so ts-patch/ttypescript setups and nest-cli.json plugin registration continue to work as before.

GraphQL Playground has been removed

@apollo/server-plugin-landing-page-graphql-playground is gone — GraphiQL is the only built-in landing page. GraphiQL is enabled by default outside production, so most apps need no configuration at all.

playground survives as a deprecated boolean alias; the object form (playground settings) is no longer accepted:

// ❌ no longer supported
GraphQLModule.forRoot({ playground: { settings: { 'editor.theme': 'light' } } });
// ✅ boolean alias still works
GraphQLModule.forRoot({ playground: true });
// ✅ preferred
GraphQLModule.forRoot({ graphiql: true });
// or with options
GraphQLModule.forRoot({ graphiql: { url: '/graphql' } });

Resolution order is graphiql → playground → default (GraphiQL when NODE_ENV !== 'production', Apollo's default landing page otherwise).

subscriptions-transport-ws has been removed

... (truncated)

Commits

• 7f0fd59 Merge branch 'master' into v14.0.0
• b6e5d43 v13.4.5
• 2dedb65 chore(deps): update apollo graphql packages
• 2a0ac23 chore(apollo): drop subscriptions-transport-ws leftovers and de-flake graphql...
• 1478cac Merge branch 'master' into v14.0.0
• c692a52 Merge pull request #4010 from nestjs/renovate/nest-monorepo
• e5e88ff test: update serialized graph snapshot for @​nestjs/core 11.2.1
• 6fd121b Merge pull request #4100 from arthimann/fix/1096-field-name-mapping
• 8318ee3 chore(deps): update nest monorepo to v11.2.1
• 9657c10 Merge pull request #4034 from nestjs/renovate/graphql-17.x
• Additional commits viewable in compare view

Updates @nestjs/common from 11.1.19 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.19 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/graphql from 13.4.0 to 14.0.0

Release notes

Sourced from @​nestjs/graphql's releases.

v14.0.0

What's Changed

@nestjs/graphql, @nestjs/apollo and @nestjs/mercurius are now native ES modules, and this major targets the Nest 12 release line.

ESM migration

All three packages are published as pure ESM ("type": "module", compiled with NodeNext) behind a proper exports map. Deep imports into build internals are no longer resolvable — import from the package root:

// ❌ no longer resolvable
import { GraphQLModule } from '@nestjs/graphql/dist/graphql.module';
// ✅
import { GraphQLModule } from '@​nestjs/graphql';

The one deep entry point that remains public is the CLI plugin:

// ✅ still supported
import { before } from '@nestjs/graphql/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 Nest app can keep require()-ing these packages unchanged. The @nestjs/graphql/plugin entry additionally ships a CJS shim (plugin.cjs), so ts-patch/ttypescript setups and nest-cli.json plugin registration continue to work as before.

GraphQL Playground has been removed

@apollo/server-plugin-landing-page-graphql-playground is gone — GraphiQL is the only built-in landing page. GraphiQL is enabled by default outside production, so most apps need no configuration at all.

playground survives as a deprecated boolean alias; the object form (playground settings) is no longer accepted:

// ❌ no longer supported
GraphQLModule.forRoot({ playground: { settings: { 'editor.theme': 'light' } } });
// ✅ boolean alias still works
GraphQLModule.forRoot({ playground: true });
// ✅ preferred
GraphQLModule.forRoot({ graphiql: true });
// or with options
GraphQLModule.forRoot({ graphiql: { url: '/graphql' } });

Resolution order is graphiql → playground → default (GraphiQL when NODE_ENV !== 'production', Apollo's default landing page otherwise).

subscriptions-transport-ws has been removed

... (truncated)

Commits

• 7f0fd59 Merge branch 'master' into v14.0.0
• b6e5d43 v13.4.5
• 2dedb65 chore(deps): update apollo graphql packages
• 2a0ac23 chore(apollo): drop subscriptions-transport-ws leftovers and de-flake graphql...
• 1478cac Merge branch 'master' into v14.0.0
• c692a52 Merge pull request #4010 from nestjs/renovate/nest-monorepo
• e5e88ff test: update serialized graph snapshot for @​nestjs/core 11.2.1
• 6fd121b Merge pull request #4100 from arthimann/fix/1096-field-name-mapping
• 8318ee3 chore(deps): update nest monorepo to v11.2.1
• 9657c10 Merge pull request #4034 from nestjs/renovate/graphql-17.x
• Additional commits viewable in compare view

Updates @nestjs/platform-express from 11.1.19 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/typeorm from 11.0.1 to 12.0.1

Release notes

Sourced from @​nestjs/typeorm's releases.

Release 12.0.1

• fix: add default condition to exports so CJS can resolve the package (01874dc)

Release 12.0.0

What's Changed

@nestjs/typeorm is now a native ES module, and the major version is aligned with the Nest 12 release line (11.0.3 → 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.

The minimum supported Node version is now >=20.19.0.

require(esm) — CommonJS still works

You do not need to convert your app to ESM. Thanks to Node's require(esm) support, CJS apps still work.

Release 11.0.3

• chore: warn instead of throwing error, partially revert #2584 (4fbe9a7)

Release 11.0.2

• Merge pull request #2616 from nestjs/renovate/cimg-node-24.x (b227891)
• Merge pull request #2605 from nestjs/renovate/postgres-18.x (60575ba)
• Merge pull request #2631 from nestjs/renovate/oxlint-monorepo (60c6218)
• Merge pull request #2632 from nestjs/renovate/actions-setup-node-6.x (5156904)
• chore(deps): update actions/setup-node action to v6 (5eb47ad)
• chore(deps): update oxlint monorepo to v1.70.0 (bfcfc7d)
• chore(deps): update nest monorepo to v11.1.27 (#2630) (55cdb77)
• chore(deps): update vitest monorepo to v4.1.9 (#2628) (2073532)
• chore(deps): update postgres docker tag to v18.4 (efdd83f)
• chore(deps): update node.js to v24.16.0 (66b9fb2)
• Merge pull request #2627 from naorpeled/feat/support-v1-of-typeorm (4c80d7c)
• ci: bump typeorm dev dependency to v1 and test both majors (959211b)
• chore(deps): update dependency @​types/node to v24.13.2 (#2626) (75f1b11)
• chore(deps): update oxlint monorepo to v1.69.0 (#2617) (5535652)
• chore(deps): update dependency prettier to v3.8.4 (#2625) (4cff37a)
• chore(deps): update dependency release-it to v20.2.0 (#2619) (27286ba)
• chore(deps): update dependency @​types/node to v24.13.1 (#2622) (2f36f10)
• chore(deps): update vitest monorepo to v4.1.8 (#2621) (704c51b)
• chore(deps): update dependency lint-staged to v17.0.7 (#2620) (7a754c9)
• chore(deps): update commitlint monorepo to v21.0.2 (#2618) (fbbd6c4)
• chore(deps): update nest monorepo to v11.1.26 (#2615) (c97a755)
• Merge pull request #2624 from AdrianoCLeao/fix/issue-2623 (051a201)
• ci: use preinstalled docker compose in CircleCI (c1160d2)
• chore(deps): update dependency vitest to v4.1.7 (#2614) (017a7cf)
• chore(deps): update dependency oxlint to v1.66.0 (#2611) (130d4af)
• chore(deps): update dependency typeorm to v0.3.30 (#2610) (94ec5c1)
• chore(deps): update dependency pg to v8.21.0 (#2609) (840651f)
• chore(deps): update dependency lint-staged to v17.0.5 (#2607) (55e6c51)

... (truncated)

Commits

• 3513624 chore(): release v12.0.1
• b36b36c Merge pull request #2685 from iflov/fix/cjs-exports-condition
• 01874dc fix: add default condition to exports so CJS can resolve the package
• 5ccaea4 chore(deps): update dependency lint-staged to v17.4.1 (#2683)
• de68dfe Merge branch 'master' of https://github.com/nestjs/typeorm
• afe5dc3 chore: bump deps to v12.0.1
• 2d2c86a Merge pull request #2682 from nestjs/renovate/cimg-node-24.x
• d40e0a5 chore(): release v12.0.0
• 36a765c chore: resolve conflicts
• d80cf31 chore: upgrade to v12 deps
• Additional commits viewable in compare view

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.19 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
• 03587a1 chore(release): publish v11.1.29 release
• 92bc05d chore: update readme
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions