Huge News!Announcing our $40M Series B led by Abstract Ventures.Learn More →
env-cmd - npm Package Versions
Changelog
7.0.0
- BREAKING: The
.envfile path resolving has been changed to allow for absolute pathing, relative pathing, and~home directory pathing. Please see Readme.md for more info about how the new pathing conventions work.
Changelog
6.0.0
- BREAKING: Fallback to default
.envfile behavior is no longer the default behavior. You must specify--fallbackoption for that behavior now. - BREAKING: A specific node version has been set in package.json. Current minimum version is
>=4.0.0. Note: the implied minimum version before this release was always4.0.0, but now it is explicitly set and could produce warnings by npm if included in projects that utilizes a node version that is less than4.0.0. - Feature: Added
--fallbackoption to allow for falling back to the default.envfile if the provided.envfile is not found. - Feature: Added ability to select multiple environments from the
.env-cmdrcfile. The environments override each other like this:development,productionwhereproductionvars overridedevelopmentvars if they share the same vars. - Bug:
env-cmdno longer crashes when it cannot find the provided.envfile. Instead, it will execute as normal, but without included any custom env vars. Note: it will still include system and shell vars.
Changelog
5.1.0
- Feature: Added new option
--no-overridethat when passed will make it so that the env file vars will not overwrite already defined env vars onprocess.envor in the shell - Updated Dev-Dependencies:
standard >= 10.0.0,sinon >= 2.0.0
Changelog
5.0.0
- BREAKING: Inline comments are no longer allowed in
.envfiles (full line comments are still allowed) - BREAKING:
.envfile no longer supports theenv varformat (onlyenv=varis allowed now) - BREAKING: Double Quotes are no longer needed when using special symbols (such as
#) in the value portion of an env var - Feature: if the given env file cannot be found, it will auto default to searching
the execution directory for a file called
.envand use that as a fallback. See README for why this is helpful. (special thanks to Alexander Praetorius)
Changelog
4.0.0
- BREAKING: In order to use double quotes as part of the env value, you must now surround those double quotes with an additional set of quotes: So
ENV1="value"->ENV1=""value""(this only applies to double quotes, single quotes continue to work as normal) - Bug: Fixed bug in the comment stripper function that would remove env values that included a
#. Now, in order to use a#in a env value, you have to surround that env value in double quotes:ENV="Some#Value". - Bug: Fixed a major bug with the
.env-cmdrcfile that would not add system env vars back in after reading the.env-cmdrcfile. This meant that system vars likePATHwould not exist when running the command.
Changelog
3.0.0
- Feature: Added ability to use an
.env-cmdrcfile to hold multiple configs - Feature: Added ability to pass in a regular
.jsfile exporting an object for your env file (special thanks to Jon Scheiding!) - Change: Updated core
cross-spawnlib to 5.0.1
Changelog
2.1.0
- Feature: Added support for
key valuemapping in env vars file - Feature: Added support for inline comments
ENV=VALUE # inline comment - Change: Will now ignore invalid lines in env vars file instead of throwing an error
- Change: Migrated all the parsing over to regex since the file format is simple enough right now to support that
- Bug: Removed old test cases for the
-e/--envflags that were not needed anymore
Changelog
2.0.0
- BREAKING: Removed the
-eand--envflags. Now it just expects the first arg toenv-cmdto be the relative path to the env file:env-cmd env_file command carg1 carg2 - Change:
ParseEnvFileis now more properly namedParseEnvString - Feature:
ParseEnvStringwill ignore comment lines (lines starting with#) - Feature:
ParseEnvStringwill ignore empty lines in env file - Bug:
ParseEnvStringwill extract the last line even if no newline (\n) exists on it