@@ -59,15 +59,16 @@ Usage: env-cmd [options] -- <command> [...args]
5959Options:
6060 -v, --version output the version number
6161 -e, --environments [envs...] The rc file environment(s) to use
62- -f, --file [path] Custom env file path or .rc file path if '-e' used (default path: ./.env or
63- ./.env-cmdrc.(js|cjs|mjs|json))
64- -x, --expand-envs Replace $var in args and command with environment variables
62+ -f, --file [path] Custom env file path or .rc file path if '-e' used (default path: ./.env or ./.env-cmdrc.(js|cjs|mjs|json))
63+ -x, --expand-envs Replace $var and ${var} in args and command with environment variables
64+ --recursive Replace $var and ${var} in env file with the referenced environment variable
6565 --fallback Fallback to default env file path, if custom env file path not found
6666 --no-override Do not override existing environment variables
6767 --silent Ignore any env-cmd errors and only fail on executed program failure.
6868 --use-shell Execute the command in a new shell with the given environment
6969 --verbose Print helpful debugging information
7070 -h, --help display help for command
71+
7172```
7273
7374## 🔬 Advanced Usage
@@ -129,14 +130,14 @@ commands together that share the same environment variables.
129130```
130131
131132### Asynchronous env file support
132-
133+
133134 EnvCmd supports reading from asynchronous ` .env ` files. Instead of using a ` .env ` file, pass in a ` .js `
134135 file that exports either an object or a ` Promise ` resolving to an object (` { ENV_VAR_NAME: value, ... } ` ). Asynchronous ` .rc `
135136 files are also supported using ` .js ` file extension and resolving to an object with top level environment
136137 names (` { production: { ENV_VAR_NAME: value, ... } } ` ).
137-
138+
138139 ** Terminal**
139-
140+
140141 ``` sh
141142 ./node_modules/.bin/env-cmd -f ./async-file.js -- node index.js
142143 ```
0 commit comments