Why env-cmd is crashing when there is no .env file ? about env-cmd HOT 6 CLOSED

Thanks for your support on this. I have no problem breaking backwards compatibility since I adhere to semver and have detailed change logs. I think adding a --fallback flag makes more sense rather than having it fallback by default. I will make that change and push a new version sometime today or tomorrow.

from env-cmd.

@gillioa Hey sorry about this. The original default behavior of env-cmd was to just do nothing and run as normal, but then the fallback PR got merged in and wiped out that default behavior.

Do you have any preference about whether to add a special flag to enable fallback or disable fallback? So something like --fallback or --disable-fallback thoughts?

from env-cmd.

I have same issue.
For example, on Heroku or Circle CI, I usually set environment vars on a setting page, not creating .env file.

If considering backward compatibility, it would be better to add --disable-fallback flag.
If not so, --fallback is good , IMO.

from env-cmd.

Wow! That’s brilliant😍

from env-cmd.

This issue has been resolved and released on npm as version 6.0.0. If you run into any problems with it, just open a new issue. Thanks for your comments and input everyone 😄

from env-cmd.

Everything went well☺️
Thanks!!

from env-cmd.