feat(expo): read .env file in upload script #3571
Merged
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
📜 Description
Read from
.env
file if it exists in the user's project directory, based on #3546 (comment)Fixes #3569
Most of the expo commands are of this form:
NODE_ENV
to development if unset (unless if the command isexpo export
, where the metro bundler will output differently depending on NODE_ENV so we default it to production).env
file -@expo/env
is a dependency of theexpo/cli
so we make a best effort to load it at runtime.💡 Motivation and Context
💚 How did you test it?
test project
📝 Checklist
sendDefaultPII
is enabled🔮 Next steps