Version 9.x breaks usage on react-scripts build about env-cmd HOT 3 CLOSED

This project does its best to adhere to semver versioning meaning any major version upgrade (1.x.x -> 2.x.x, 2.x.x -> 3.x.x, etc...) could cause breaking non-backwards compatible changes. This is the case when upgrading from version 8.x.x -> 9.x.x 🙁

In the changelog it states that the options have changed for 9.x.x and up 😄

For your specific case you need to provide the -f flag in order to read from a custom file path. So env-cmd .env.production react-scripts build -> env-cmd -f .env.production react-scripts build. This was done in order to better future proof the lib from new features that are requested in the future.

See examples repo for more specific examples regarding env file usage or you can also view the Help section of the ReadMe file (Note: you can also do env-cmd --help to view the same help menu found in the above Help section) 😄

Related to: #61

Sorry about the breakage 🙁
Thanks for using this tool and hopefully that helps clear up your issue 😃

from env-cmd.

Thank you for the advice. I fully understand and respect the reasoning behind the breaking change; not a problem.

Thank also for all your hard graft on this project and for making it freely available. I'm very grateful - It's a valuable, useful tool, and your work is very much appreciated.

from env-cmd.

Closing due to inactivity

from env-cmd.