[build-tools] Use production mode for app config, prebuild, and Expo Doctor - #4180
Draft
ramonclaudio wants to merge 11 commits into
Draft
[build-tools] Use production mode for app config, prebuild, and Expo Doctor#4180ramonclaudio wants to merge 11 commits into
ramonclaudio wants to merge 11 commits into
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #4180 +/- ##
==========================================
+ Coverage 63.54% 63.68% +0.14%
==========================================
Files 1028 1030 +2
Lines 47054 47088 +34
Branches 9891 9894 +3
==========================================
+ Hits 29898 29982 +84
+ Misses 17055 17005 -50
Partials 101 101 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
This was referenced Aug 12, 2026
ramonclaudio
force-pushed
the
@ramonclaudio/dvt-119-eas-config-mode-handoff
branch
from
August 13, 2026 13:48
0822cb4 to
bdc5d2b
Compare
3 tasks
ramonclaudio
force-pushed
the
@ramonclaudio/dvt-119-eas-config-mode-handoff
branch
from
August 16, 2026 14:13
ad8a21c to
0822cb4
Compare
ramonclaudio
added a commit
to expo/expo
that referenced
this pull request
Aug 17, 2026
# Why The EAS changes in [#4180](expo/eas-cli#4180) tell Expo to use development or production mode when loading app config, so we needed a temporary internal environment variable that Expo reads and removes before app config loads. # How I added `__EXPO_CONFIG_MODE` as an internal handoff that `@expo/env` reads and removes before Expo loads the dotenv files and app config. I blocked `.env` files from setting the handoff and updated `getOriginalEnv()` and `getOriginalEnvValue()` to exclude dotenv values inherited from a parent process. We still use `EAS_BUILD` as the production fallback for older EAS versions. # Test Plan Tests and package checks pass. # Checklist - [x] I added a `changelog.md` entry and rebuilt the package sources according to [this short guide](https://github.com/expo/expo/blob/main/CONTRIBUTING.md#-before-submitting) - [ ] This diff will work correctly for `npx expo prebuild` & EAS Build (eg: updated a module plugin). - [ ] Conforms with the [Documentation Writing Style Guide](https://github.com/expo/expo/blob/main/guides/Expo%20Documentation%20Writing%20Style%20Guide.md)
ramonclaudio
force-pushed
the
@ramonclaudio/dvt-119-eas-config-mode-handoff
branch
from
August 18, 2026 22:23
0822cb4 to
e3e4ea2
Compare
|
✅ Thank you for adding the changelog entry! |
ramonclaudio
restored the
@ramonclaudio/dvt-119-eas-config-mode-handoff
branch
August 18, 2026 22:54
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why
EAS Build can use an existing
NODE_ENVwhen loading app config or running Expo commands, which can make it load different env files for the same build.How
I updated EAS Build to use
productionmode for app config, prebuild, and Expo Doctor and kept the users env for dep installs.Test Plan
Tests and CI checks pass.