This pull request adds support for expanding environment variable
expansion support. Closes#91
Since the user controls the call site of cmd-env, it only supports
basic UNIX style $var format. `%var%` (windows) or `${var}` is not
supported. However, you can escape variable expansion by escaping
the dollar sign like so `\$`.
Signed-off-by: omeid matten <public@omeid.me>
- Removed all the various eslint dependencies and added ts-standard
- Updated Readme file with some minor changes
- Updated dist folder to have one level again
* Added env default locations to match rc file locations
* Updated README to clarify all supported files and their formats
* Added new test to verify all env files are searched for
- 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
- 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
* 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
- 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”
