feat(cli): load .env
files before running any command
#2320
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.
Type of change (check at least one)
Does this change require a documentation update? (Check one)
Current behavior
When running CLI commands, any environment variables set in
.env
-files are not respected. For instance, runningsanity graphql deploy
,sanity deploy
andsanity users list
uses the values defined insanity.json
instead of respecting any.env
file overrides.Description
This PR ensures any
.env
-file is read and used before running any CLI commands.Fixes #2318
Note for release
.env
files will now be loaded before running any Sanity CLI commandChecklist
[some-package] PR title (#123)