Skip to content

chore(deps)(deps-dev): bump @nestjs/testing from 11.2.1 to 12.0.1 - #193

Closed
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/nestjs/testing-12.0.1
Closed

chore(deps)(deps-dev): bump @nestjs/testing from 11.2.1 to 12.0.1#193
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/npm_and_yarn/nestjs/testing-12.0.1

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Aug 31, 2026

Copy link
Copy Markdown
Contributor

Bumps @nestjs/testing from 11.2.1 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 playgroundgraphiql 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
  • e255755 chore: resolve conflicts, minor fixes
  • 5d1b19b Merge branch 'master' into v12.0.0
  • eb49dd1 test(testing): Add unit tests for @​nestjs/testing package
  • 68dfc23 Merge branch 'master' into v12.0.0
  • c470ddf Merge branch 'master' into v12.0.0
  • 415e4d3 fix(testing): use try load package insted (dummy load)
  • Additional commits viewable in compare view

@dependabot @github

dependabot Bot commented on behalf of github Aug 31, 2026

Copy link
Copy Markdown
Contributor Author

Labels

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

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

@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Aug 31, 2026
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/nestjs/testing-12.0.1 branch from 64060fd to 55a7c87 Compare August 31, 2026 07:31
Bumps [@nestjs/testing](https://github.com/nestjs/nest/tree/HEAD/packages/testing) from 11.2.1 to 12.0.1.
- [Release notes](https://github.com/nestjs/nest/releases)
- [Commits](https://github.com/nestjs/nest/commits/v12.0.1/packages/testing)

---
updated-dependencies:
- dependency-name: "@nestjs/testing"
  dependency-version: 12.0.1
  dependency-type: direct:development
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/npm_and_yarn/nestjs/testing-12.0.1 branch from 55a7c87 to 020e712 Compare September 1, 2026 10:54
ihabkhaled added a commit that referenced this pull request Sep 1, 2026
Coordinated bump of @nestjs/common, core, platform-express, testing,
schedule, mongoose and schematics to their v12 releases across all 18
NestJS services and the 4 shared packages that depend on them (closing
dependabot PRs #188, #190, #193, #196, which each only bumped one
package and left the tree in a broken mixed-version state).

NestJS 12's common/core/testing packages ship as pure ESM with no
CommonJS build, which this repo's TypeScript config (Node16 module
resolution) rejects outright. Verified empirically that the minimal,
non-invasive fix is `module: esnext` + `moduleResolution: bundler` in
each workspace's tsconfig — TypeScript stops requiring extensions on
relative imports (avoiding a rewrite of every import in the codebase),
while `"type": "module"` in package.json makes Node's own ESM loader
handle the compiled output correctly. tsc-alias's -f flag adds the
`.js` extensions to compiled output that Node's loader still needs.

Knock-on fixes, each proven with an actual boot (not just a green
typecheck):

- Prisma's generated client is copied into dist/, not compiled by tsc;
  a new tools/typescript/copy-generated-prisma.mjs step runs between
  the compile and the tsc-alias pass so the copy exists before
  tsc-alias resolves the extension on that import.
- Auth-service and routing-service's plain-node Prisma seed scripts
  (seed.js and friends, using require()) are renamed .cjs, since a
  parent "type": "module" makes Node parse a bare .js as ESM.
  prisma.config.ts and the seed/seed:permissions package.json scripts
  updated to match.
- Jest keeps running as CommonJS (switching it to ESM breaks the
  `jest.mock`/`jest.fn` globals in every spec file) but needs
  @nestjs/*'s compiled JS transformed back to CJS for tests only,
  via a babel-jest pass scoped to node_modules/@nestjs plus a
  reflect-metadata setupFile (v12 no longer pulls it in as a side
  effect). @babel/core is pinned to the stable v7 line, not v8 --
  babel-plugin-transform-import-meta's v8-only release conflicts with
  this repo's other Babel 7 consumers.
- nestjs-pino bumped 4.6.1 -> 5.0.0 (only version whose peer range
  allows @nestjs/common v12).
- @nestjs/throttler has not yet published a v12-compatible peer range
  (latest is 6.5.0, capped at ^11); Docker's from-scratch dependency
  install (no lockfile, unlike CI's `npm ci`) needs --legacy-peer-deps
  to accept that known-safe mismatch, added to every service's
  Dockerfile and Dockerfile.dev.

Verified end-to-end, not just gated: typecheck, lint, build and test
green across all 18 services and 6 shared packages, and a real `docker
build` + `docker run` of claw-health-service reaches "Nest application
successfully started" inside the actual production image.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@dependabot @github

dependabot Bot commented on behalf of github Sep 1, 2026

Copy link
Copy Markdown
Contributor Author

Looks like @nestjs/testing is up-to-date now, so this is no longer needed.

@dependabot dependabot Bot closed this Sep 1, 2026
@dependabot
dependabot Bot deleted the dependabot/npm_and_yarn/nestjs/testing-12.0.1 branch September 1, 2026 13:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants