fix(deps): update nest monorepo (major)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
@nestjs/cli	~10.4.0 -> ~11.0.0
@nestjs/common (source)	~10.4.0 -> ~11.0.0
@nestjs/config	~3.3.0 -> ~4.0.0
@nestjs/core (source)	~10.4.0 -> ~11.0.0
@nestjs/platform-express (source)	~10.4.0 -> ~11.0.0
@nestjs/testing (source)	~10.4.0 -> ~11.0.0

---

Release Notes

nestjs/nest-cli (@​nestjs/cli)

v11.0.2

Compare Source

• fix: swc compiler does not watch files (8aaa9df)

v11.0.1

Compare Source

v11.0.0

Compare Source

Migration guide: https://docs.nestjs.com/migration-guide

Features and improvements

• feat(schematics): list schematics from extended collections #​2096
• feat: nest build --all flag #​2312
• feat: add flag to disable shell mode for nest start --watch #​2522
• feat!: drop uncommon variants of nest cli config file name #​2769
• feat: add support for --env-file flag #​2818

Dependencies

• fix(deps): update dependency glob to v11 #​2788
• chore/upgrade inquirer package #​2718
• fix(deps): update dependency chokidar to v4 #​2734
• fix(deps): update angular-cli monorepo to v19 #​2811

nestjs/nest (@​nestjs/common)

v11.0.5

Compare Source

v11.0.4

Compare Source

v11.0.3

Compare Source

v11.0.2

Compare Source

v11.0.1

Compare Source

v11.0.0

Compare Source

nestjs/config (@​nestjs/config)

v4.0.0

Compare Source

Breaking changes

The order in which configuration variables are read by the ConfigService#get method has been updated. The new order is:

• Internal configuration (config namespaces and custom config files)
• Validated environment variables (if validation is enabled and a schema is provided)
• The process.env object

Previously, validated environment variables and the process.env object were read first, preventing them from being overridden by internal configuration. With this update, internal configuration will now always take precedence over environment variables.

Additionally, the ignoreEnvVars configuration option, which previously allowed disabling validation of the process.env object, has been deprecated. Instead, use the validatePredefined option (set to false to disable validation of predefined environment variables). Predefined environment variables refer to process.env variables that were set before the module was imported. For example, if you start your application with PORT=3000 node main.js, the PORT variable is considered predefined. However, variables loaded by the ConfigModule from a .env file are not classified as predefined.

A new skipProcessEnv option has also been introduced. This option allows you to prevent the ConfigService#get method from accessing the process.env object entirely, which can be helpful when you want to restrict the service from reading environment variables directly.

Changelog

• chore: update config attributes to more self descriptive names (c2eaf04)
• chore(deps): update nest monorepo to v11 (1c20713)
• feat: order of reading variables, add skip predefined (c53c63c)

nestjs/nest (@​nestjs/core)

v11.0.5

Compare Source

v11.0.4

Compare Source

v11.0.3

Compare Source

v11.0.2

Compare Source

v11.0.1

Compare Source

v11.0.0

Compare Source

nestjs/nest (@​nestjs/platform-express)

v11.0.5

Compare Source

v11.0.4

Compare Source

v11.0.3

Compare Source

v11.0.2

Compare Source

v11.0.1

Compare Source

v11.0.0

Compare Source

nestjs/nest (@​nestjs/testing)

v11.0.5

Compare Source

v11.0.4

Compare Source

v11.0.3

Compare Source

v11.0.2

Compare Source

v11.0.1

Compare Source

v11.0.0

Compare Source

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @golevelup/nestjs-discovery@4.0.1
npm warn Found: @nestjs/common@11.0.5
npm warn node_modules/@nestjs/common
npm warn   @nestjs/common@"~11.0.0" from the root project
npm warn   4 more (@nestjs/config, @nestjs/core, ...)
npm warn
npm warn Could not resolve dependency:
npm warn peer @nestjs/common@"^10.x" from @golevelup/nestjs-discovery@4.0.1
npm warn node_modules/@golevelup/nestjs-discovery
npm warn   @golevelup/nestjs-discovery@"4.0.1" from nest-commander@3.15.0
npm warn   node_modules/nest-commander
npm warn
npm warn Conflicting peer dependency: @nestjs/common@10.4.15
npm warn node_modules/@nestjs/common
npm warn   peer @nestjs/common@"^10.x" from @golevelup/nestjs-discovery@4.0.1
npm warn   node_modules/@golevelup/nestjs-discovery
npm warn     @golevelup/nestjs-discovery@"4.0.1" from nest-commander@3.15.0
npm warn     node_modules/nest-commander
npm warn ERESOLVE overriding peer dependency
npm warn While resolving: @golevelup/nestjs-discovery@4.0.1
npm warn Found: @nestjs/core@11.0.5
npm warn node_modules/@nestjs/core
npm warn   @nestjs/core@"~11.0.0" from the root project
npm warn   2 more (@nestjs/platform-express, @nestjs/testing)
npm warn
npm warn Could not resolve dependency:
npm warn peer @nestjs/core@"^10.x" from @golevelup/nestjs-discovery@4.0.1
npm warn node_modules/@golevelup/nestjs-discovery
npm warn   @golevelup/nestjs-discovery@"4.0.1" from nest-commander@3.15.0
npm warn   node_modules/nest-commander
npm warn
npm warn Conflicting peer dependency: @nestjs/core@10.4.15
npm warn node_modules/@nestjs/core
npm warn   peer @nestjs/core@"^10.x" from @golevelup/nestjs-discovery@4.0.1
npm warn   node_modules/@golevelup/nestjs-discovery
npm warn     @golevelup/nestjs-discovery@"4.0.1" from nest-commander@3.15.0
npm warn     node_modules/nest-commander
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: nest-commander@3.15.0
npm error Found: @nestjs/common@11.0.5
npm error node_modules/@nestjs/common
npm error   @nestjs/common@"~11.0.0" from the root project
npm error   peer @nestjs/common@"^10.0.0 || ^11.0.0" from @nestjs/config@4.0.0
npm error   node_modules/@nestjs/config
npm error     @nestjs/config@"~4.0.0" from the root project
npm error   3 more (@nestjs/core, @nestjs/platform-express, @nestjs/testing)
npm error
npm error Could not resolve dependency:
npm error peer @nestjs/common@"^8.0.0 || ^9.0.0 || ^10.0.0" from nest-commander@3.15.0
npm error node_modules/nest-commander
npm error   nest-commander@"~3.15.0" from the root project
npm error   peer nest-commander@"^2.5.0 || ^3.0.0" from nest-commander-testing@3.3.0
npm error   node_modules/nest-commander-testing
npm error     dev nest-commander-testing@"~3.3.0" from the root project
npm error
npm error Conflicting peer dependency: @nestjs/common@10.4.15
npm error node_modules/@nestjs/common
npm error   peer @nestjs/common@"^8.0.0 || ^9.0.0 || ^10.0.0" from nest-commander@3.15.0
npm error   node_modules/nest-commander
npm error     nest-commander@"~3.15.0" from the root project
npm error     peer nest-commander@"^2.5.0 || ^3.0.0" from nest-commander-testing@3.3.0
npm error     node_modules/nest-commander-testing
npm error       dev nest-commander-testing@"~3.3.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2025-01-23T22_04_07_289Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2025-01-23T22_04_07_289Z-debug-0.log