- All env-cmd-examples repo cases passing
- Added support for default .env-cmdrc.json file
- Added flag and help text lib
- Split up project into more reasonable files/chunks of code
- Updated copyright year to 2019
* Fix spawn and parent process killing
- Implemented a broader solution to killing the parent/spawned process
that includes hooks for certain specific signals and then the generic
node exit event
- Added test cases to support the new termination solution
* Updated a bunch of node dependencies
* Updated change log
* Allow for using absolute pathing, ~ pathing, and relative pathing
* Add test cases for `./` and `../` pathing
* Update Readme file with new path rules
* Refactored fallback behavior to require a --fallback flag
- By default env-cmd will no longer crash if .env or .env-cmdrc files
are not found
- In order to use the old default .env file fallback functionality a
--fallback flag must be passed
* Update minimum nodejs version and update Readme file
* Fix coverage
* Reduce minimum nodejs version down to v4
* Minor readme tweaks
If a repository contains a `.env` example file or - in case of a private repository - a `.env` file with production values,
a developer can add a local (e.g. `.env.local` file to `.gitignore`) and feed it to `env-cmd`.
So in development a custom local configuration can be used, but in production, `env-cmd` falls back to `.env`
- After retrieving user set envs from a file, add the system envs back
into the envs object so that envs like PATH, etc… will exist for the
spawned command
- Fixed a bug that caused a # symbol in the env value to be interpreted
as an inline comment
- When you want to include a # in you value, you need to wrap it in
double quotes: ENV=“some#symbol value”
- Moved over to using regex for parsing the env file
- Added support for inline comments
- Added support for `key value` pairing file format
- Will now ignore invalid lines in env file, instead of throwing an error
- Removed old test cases
- Added more specific test cases
- Removed the -e/--env flags in favor of just requiring the first arg to
env-cmd to be the relative path to the env file
- Comments are now valid in env files using the #
- Empty lines in env file are now ignored
- Fixed bug env file no longer needs to end on a newline
