build(deps): Bump @nestjs/config from 3.3.0 to 4.0.1

[dependabot]

Bumps @nestjs/config from 3.3.0 to 4.0.1.

Release notes

Sourced from @​nestjs/config's releases.

Release 4.0.1

• fix: validate predefined condition #1970 (79d82d6)
• feat: allow to use symbol as a token (99d8bca)

Release 4.0.0

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)

Commits

• da628f1 chore(): release v4.0.1
• 79d82d6 fix: validate predefined condition #1970
• 5937fb5 Merge pull request #1972 from kishieel/master
• 0bf6f62 chore(deps): update dependency prettier to v3.5.3 (#1976)
• c08aba2 chore(deps): update dependency @​types/node to v22.13.8 (#1974)
• 6f43afd chore(deps): update dependency @​types/lodash to v4.17.16 (#1973)
• fa5af20 chore(deps): update nest monorepo to v11.0.11 (#1971)
• 408ed25 style: fix formatting
• 9f6266b style: format code
• 99d8bca feat: allow to use symbol as a token
• 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 merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Summary by Sourcery

Build:

• Update @nestjs/config dependency from 3.3.0 to 4.0.1.

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[sourcery-ai]

Reviewer's Guide by Sourcery

This pull request updates the @nestjs/config dependency from version 3.3.0 to 4.0.1. This includes updating the core library, as well as updating the lock file and package.json file.

Updated class diagram for ConfigService

classDiagram
  class ConfigService {
    - env: process.env
    - internalConfig: Map
    + get(key: string): string | undefined
  }
  note for ConfigService "The order in which configuration variables are read by the ConfigService#get method has been updated. The new order is: Internal configuration, Validated environment variables, The process.env object."

Loading

File-Level Changes

Change	Details	Files
Update @nestjs/config dependency from version 3.3.0 to 4.0.1.	Update @nestjs/config to version 4.0.1. Update the version of @nestjs/common to be compatible with the new @nestjs/config version. Update dotenv and dotenv-expand dependencies.	pnpm-lock.yaml package.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!
• Generate a plan of action for an issue: Comment @sourcery-ai plan on
  an issue to generate a plan of action for it.

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

We have skipped reviewing this pull request. It seems to have been created by a bot (hey, dependabot[bot]!). We assume it knows what it's doing!