🐛 .env file override order is slightly off compared to dotenv-flow

[walkerdb]

dotenv-flow describes their override order as the following:

1. base .env
2. .env.local
3. .env.[environment]
4. .env.[environment].local
5. ...local environment variables

However this library's current override order is:

1. base .env
2. .env.[environment]
3. .env.local
4. .env.[environment].local
5. ...local environment variables

with 2 and 3 swapped compared to dotenv-flow. This order is defined by a series of object assignments here: https://github.com/goatandsheep/react-native-dotenv/blob/main/index.js#L93-L94

Can this be switched around to match dotenv-flow's approach instead?

[github-actions]

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/397

[goatandsheep]

That is bad and sloppy. I'll take a look

[elitenas]

I am still seeing this as an issue.

.env.development is taking priority over .env.local

[goatandsheep]

I will have to double check

[elitenas]

@goatandsheep .env.local takes priority over .env.production which is good. I am only seeing this issue between .env.local and .env.development

More info on order below:

https://create-react-app.dev/docs/adding-custom-environment-variables/#what-other-env-files-can-be-used

[github-actions]

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/397

[goatandsheep]

Hi @elitenas can you send me your babel configuration / reproduction details?

[elitenas]

Here is a barebone repro project: https://drive.google.com/file/d/1U9sGA3cvVLKW6caPdSVvip79u5ByH7E-/view?usp=sharing

In the repro project, i am outputting the value of API_URL. I am seeing the value show up as http://testing.com instead of http://testing222.com.

even though .env.local should have higher priority

[goatandsheep]

Hi @elitenas I'm closing this as this is an old issue and the new issue is #415