fix(config): don't interpolate env variables with undefined
value
#8013
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.
Types of changes
Description
fixing #7990 and #8013 by preserving variables with
undefined
value (note that this is not exactly howdontenv-expand
works, they do replace with an empty string but since we already have a fork and has bug forundefined
it can at least resolve current issue)In rare cases to avoid conflicting part of token with env variables, it is adviced to escape like this:
Some ideas for future:
Token="..."
syntax for.env
to escape but it is being removed by dotenv (here) so not much chance unless they support it or we use a fork.${...}
syntax for interpolation (suggested by @galvez) but not possible since we need a fork ofdotenv
and it is a breaking changeruntimeConfig
notdotenv
which is still a breaking changeChecklist: