# nestjs/release
NestJS v12.0.0
importance: highbreakingdeprecationmigrationfeature
NestJS v12 introduces ESM-ready packages, Standard Schema support, a rebuilt CLI, and native observability. It requires Node.js v20.19+ or v22.12+ and includes several breaking changes.
affected
All NestJS users upgrading from v11 to v12 are affected, particularly those using custom bootstrapping, bundler configurations, or older Node.js versions.
action
Follow the migration guide and use `nest upgrade` to automate parts of the upgrade process.
release_signals
-Packages now ship as ESM. While CommonJS applications continue to work via `require(esm)`, custom bootstrapping, bundler, and test-runner configurations may need review.
-Node.js v20.19+ or v22.12+ is now required. The 21.x line is not supported.
-Lifecycle hooks and other internal changes may affect applications relying on undocumented behaviors.
!The `--webpack` and `--webpackPath` flags in the CLI are deprecated in favor of `--builder rspack`.
!The `angular` schematic has been removed.
+ESM-ready packages with optional migration for existing CommonJS applications.
+First-class Standard Schema support for validation and serialization.
+Native observability through the new `@nestjs/observe` SDK.
migration_steps3 steps
- 01Upgrade the CLI first with `npm i -g @nestjs/cli@latest`.
- 02Run `nest upgrade` from the root of your project to apply mechanical migration steps.
- 03Review the migration guide at https://docs.nestjs.com/migration-guide for manual adjustments.
code_snippet
```ts
@Post()
create(@Body({ schema: createUserSchema }) body: CreateUserDto) {
return this.usersService.create(body);
}
```# community_signal
How useful is this release to your stack?
—
net score
Sign in with GitHub to cast your vote.
Sign in with GitHub to vote
You’ll return to this release, then choose your vote.