-
-
Notifications
You must be signed in to change notification settings - Fork 45
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Follow dotenv-flow variable precedence #491
Comments
Hey, thank you for opening this issue! 🙂 To boost priority on this issue and support open source please tip the team at https://issuehunt.io/r/goatandsheep/react-native-dotenv/issues/491 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The documentation for this library mentions that it follows the
dotenv-flow
for multi-environment variable loading. (link)However, I've noticed a minor difference when compared to the
dotenv-flow
.According to the
dotenv-flow
's variables overwriting priority, the variable merging order should be:.env
.env.local
.env.development
.env.development.local
But in practice, when
NODE_ENV='development'
, the order of variable merging in this library seems to be:.env
.env.development
.env.local
.env.development.local
This had lead some confusions, for instance, mode-specific variables being unexpectedly overwritten by variables from the
.env.local
file.The text was updated successfully, but these errors were encountered: