DEV Community


Discussion on: Managing .env variables for provisional builds with Create React App

consciousness_dev profile image
Ario Setiawan

[Update] But when i run it with your suggestion, it still have an error

npm run start:local

> apps@0.1.0 start:local /home/me/react/apps
> env-cmd -f .env.local react-script start

spawn react-script ENOENT
npm ERR! errno 129
npm ERR! apps@0.1.0 start:local: `env-cmd -f .env.local react-script start`
npm ERR! Exit status 129
npm ERR! 
npm ERR! Failed at the apps@0.1.0 start:local script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR! A complete log of this run can be found in:
npm ERR!     /home/me/.npm/_logs/2019-12-04T01_34_08_907Z-debug.log
Thread Thread
donghyukjacobjang profile image
Donghyuk (Jacob) Jang Author

I have tried in the example repository, and it seems to be working fine. You may have some conflicts.

The example repository is

You will be able to find .env.local and start:local in package.json.

Since I cannot see all your config and settings, providing you the example repo is the best thing I can do at the moment.

Please let me know if you have questions.

Donghyuk (Jacob) Jang

Thread Thread
consciousness_dev profile image
Ario Setiawan

Pardon Me, i'd typo on 'react-script', which is true 'react-scripts', with 's' in the end of script it, thanks a lot! :O