Open jleem99 opened 9 months ago
The documentation for this library mentions that it follows the dotenv-flow for multi-environment variable loading. (link)
dotenv-flow
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:
NODE_ENV='development'
This had lead some confusions, for instance, mode-specific variables being unexpectedly overwritten by variables from the .env.local file.
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
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 thedotenv-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.