Skip to content
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

Make .env.local created by env-sync command not to be over .env.production #33

Open
ezhlobo opened this issue Dec 11, 2020 · 0 comments

Comments

@ezhlobo
Copy link
Member

ezhlobo commented Dec 11, 2020

We used to use both .env.local and .env.production at the same time... But after upgrading to the latest react-scripts (v4) we got wrong resolving.

For react-scripts build script:

-.env.production.local, .env.production, .env.local, .env
+.env.production.local, .env.local, .env.production, .env

I believe dreact env-sync should generate file with different name in order not to be more prioritized than any other environment vars and also should be ignored by default .gitignore file. The best candidate seems to be .env.development.local.

Alternatively we can generate either .env.development or .env but ask to. put it into gitignore or do that automatically.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant