Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More →
env-cmd - npm Package Versions
Changelog
10.1.0
- Feature: Added support for expanding vars using the
-xflag. Note: only supports$varsyntax - Feature: Added support for
--silentflag that ignores env-cmd errors and missing files and only terminates on caught signals - Feature: Added a new
--verboseflag that prints additional debugging info toconsole.info - Upgrade: Upgraded dependency
commanderto4.x - Upgrade: Upgraded devDependencies
sinon,nyc, andts-standard - Fix: Handle case where the termination signal is the termination code
Changelog
10.0.1
- Fix: Fixed bug introduced by strict equal checking for
undefinedwhen the value wasnull. This bug caused most executions ofenv-cmdto fail with an error, when in fact no error had occurred.
Changelog
10.0.0
- BREAKING: Typescript now targets ES2017
- Fix: Default RC files will now properly be searched
- Change: Fixed some documentation issues
- Change: Use
ts-standardinstead ofeslintfor linting
Changelog
9.0.3
- Fix: Use global flag on regex when parsing and preserving newline characters in env values (thanks to MaximTovstashev)
Changelog
9.0.2
- Fix: CLI will now exit with non-zero error code when an error is encountered (thanks to blagh)
Changelog
9.0.1
- BREAKING: Fixed major bug that required passing
--in order to pass flags to the command. Normally I release major breaking changes as major versions, but this was a bug and no documentation anywhere states using--as intended or official behavior. - Change: Fixed some documentation issues
- Change:
npm run lintcommand now includes callingtscto check for typescript errors
Changelog
9.0.0
- BREAKING: Converted project to Typescript
- BREAKING: Changes to all option flags, see docs for new options
- BREAKING: Dropping support for node v4 and v6
- Change: Updated all dependencies
- Change: Update package-lock.json file
- Feature: Added support for asynchronous .env and .rc files
- Feature: Added support for a programmatic API
- Feature: Added --use-shell option (thanks to nidkil)
- Fix: Keep newline (
\n) characters intact when parsing env files - Change: Added node v10 and v12 to build automation
- Change: Updated Readme file to reflect new options and CLI changes
Changelog
8.0.0
- BREAKING: Stripe out spaces around the
keyandvaluein an env file. In order to include a beginning/ending space in an env var value, you need to surround the value in double or single quotes.ENV = " Value" - Bug: Fixed some bugs around how the parent process and spawn processes are killed
- Change: Updated a number of core libraries:
cross-spawn,coveralls,istanbul -> nyc,mocha,proxyquire,sinon,standard