fix(deps): update dependency @nestjs/config to v4 #138
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^3.3.0
->^4.0.0
Release Notes
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:process.env
objectPreviously, 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 theprocess.env
object, has been deprecated. Instead, use thevalidatePredefined
option (set tofalse
to disable validation of predefined environment variables). Predefined environment variables refer toprocess.env
variables that were set before the module was imported. For example, if you start your application withPORT=3000 node main.js
, thePORT
variable is considered predefined. However, variables loaded by theConfigModule
from a.env
file are not classified as predefined.A new
skipProcessEnv
option has also been introduced. This option allows you to prevent theConfigService#get
method from accessing theprocess.env
object entirely, which can be helpful when you want to restrict the service from reading environment variables directly.Changelog
c2eaf04
)1c20713
)c53c63c
)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 becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.