env-cmd - npm Package Compare versions
Comparing version 9.0.1 to 9.0.2
| # Changelog | ||
| ## 9.0.2 | ||
| - **Fix**: CLI will now exit with non-zero error code when an error is encountered (thanks to blagh) | ||
| ## 9.0.1 | ||
| - **BREAKING**: Fixed major bug that required passing `--` inorder to pass flags to the command. | ||
| - **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 | ||
@@ -10,2 +16,3 @@ anywhere states using `--` as intended or official behavior. | ||
| ## 9.0.0 | ||
| - ***BREAKING***: Converted project to Typescript | ||
@@ -24,8 +31,11 @@ - ***BREAKING***: Changes to all option flags, see docs for new options | ||
| ## 8.0.2 | ||
| - **Change**: Updated dependencies and packages.json to fix `npm audit` concerns. | ||
| ## 8.0.1 | ||
| - **Bug**: Properly propagate child process exit signals and codes to parent process | ||
| ## 8.0.0 | ||
| - ***BREAKING***: Stripe out spaces around the `key` and `value` in 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"` | ||
@@ -36,2 +46,3 @@ - **Bug**: Fixed some bugs around how the parent process and spawn processes are killed | ||
| ## 7.0.0 | ||
| - ***BREAKING***: The `.env` file path resolving has been changed to allow for absolute pathing, relative pathing, and `~` home directory pathing. Please | ||
@@ -41,2 +52,3 @@ see Readme.md for more info about how the new pathing conventions work. | ||
| ## 6.0.0 | ||
| - ***BREAKING***: Fallback to default `.env` file behavior is no longer the default behavior. You must specify `--fallback` option for that behavior now. | ||
@@ -52,2 +64,3 @@ - ***BREAKING***: A specific node version has been set in package.json. Current minimum version is `>=4.0.0`. *Note: the implied minimum version | ||
| ## 5.1.0 | ||
| - **Feature**: Added new option `--no-override` that when passed will make it so that the env file | ||
@@ -58,2 +71,3 @@ vars will not overwrite already defined env vars on `process.env` or in the shell | ||
| ## 5.0.0 | ||
| - ***BREAKING***: Inline comments are no longer allowed in `.env` files (full line comments are still allowed) | ||
@@ -67,2 +81,3 @@ - ***BREAKING***: `.env` file no longer supports the `env var` format (only `env=var` is allowed now) | ||
| ## 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) | ||
@@ -73,2 +88,3 @@ - **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"`. | ||
| ## 3.0.0 | ||
| - **Feature**: Added ability to use an `.env-cmdrc` file to hold multiple configs | ||
@@ -79,5 +95,7 @@ - **Feature**: Added ability to pass in a regular `.js` file exporting an object for your env file (special thanks to Jon Scheiding!) | ||
| ## 2.2.0 | ||
| - **Feature**: Added support for .json env files (special thanks to Eric Lanehart!) | ||
| ## 2.1.0 | ||
| - **Feature**: Added support for `key value` mapping in env vars file | ||
@@ -91,2 +109,3 @@ - **Feature**: Added support for inline comments `ENV=VALUE # inline comment` | ||
| ## 2.0.0 | ||
| - ***BREAKING***: Removed the `-e` and `--env` flags. Now it just expects the first arg to `env-cmd` to be the relative path to the env file: `env-cmd env_file command carg1 carg2` | ||
@@ -99,2 +118,3 @@ - **Change:** `ParseEnvFile` is now more properly named `ParseEnvString` | ||
| ## 1.0.1 | ||
| - Fixed badges | ||
@@ -106,2 +126,3 @@ - Added .npmignore | ||
| ## 1.0.0 | ||
| - Initial release |
@@ -26,3 +26,9 @@ "use strict"; | ||
| // Run EnvCmd | ||
| return exports.EnvCmd(parsedArgs); | ||
| try { | ||
| return yield exports.EnvCmd(parsedArgs); | ||
| } | ||
| catch (e) { | ||
| console.error(e); | ||
| return process.exit(1); | ||
| } | ||
| }); | ||
@@ -29,0 +35,0 @@ } |
| { | ||
| "name": "env-cmd", | ||
| "version": "9.0.1", | ||
| "version": "9.0.2", | ||
| "description": "Executes a command using the environment variables in an env file", | ||
@@ -19,3 +19,4 @@ "main": "dist/index.js", | ||
| "lint": "eslint --fix ./src/**/*.ts ./test/**/*.ts && tsc --noEmit", | ||
| "build": "tsc" | ||
| "build": "tsc", | ||
| "watch": "tsc -w" | ||
| }, | ||
@@ -22,0 +23,0 @@ "repository": { |
@@ -6,3 +6,3 @@ [](https://travis-ci.org/toddbluhm/env-cmd) | ||
| [](https://www.npmjs.com/package/env-cmd) | ||
| [](http://standardjs.com/) | ||
| [](http://standardjs.com/) [](https://greenkeeper.io/) | ||
@@ -39,3 +39,10 @@ # env-cmd | ||
| ## Using custom env file path | ||
| To use a custom env filename or path, pass the `-f` flag. This is a major breaking change from prior versions < 9.0.0 | ||
| **Terminal** | ||
| ```sh | ||
| ./node_modules/.bin/env-cmd -f ./custom/path/.env node index.js | ||
| ``` | ||
| ## 📜 Help | ||
@@ -42,0 +49,0 @@ ``` |
New alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Fixed alerts
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
Improved metrics
- Total package byte prevSize
- increased by1.56%
40272
- Lines of code
- increased by0.97%
622
- Number of lines in readme file
- increased by3.37%
215