- Complete rewrite and reorganization
- Expose a usable programmatic API
- Support Async env files by accepting javascript files
- Update all libraries/dependencies
- Support for more options in the future by using commanderjs
- More thorough test cases and code-coverage
- Better handling of signal terminations for both parent and child
processes
- Use ESLint Standard with Typescript
- Add support for --use-shell
- Complete rewrite and reorganization
- Expose a usable programmatic API
- Support Async .env files by accepting javascript files
- Update all libraries/dependencies
- Support for more options in the future by using commanderjs
- More thorough test cases and code-coverage
- Better handling of signal terminations for both parent and child
processes
- Use ESLint Standard with Typescript
- 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
- Drop support for node v4
- Update dev dependencies sinon and nyc
- Updated package-lock file
- Updated license file year text
- Added examples link to readme
- Added node 10 version to automated testing
* 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`
