Most Windows command prompts will choke when you set environment variables with
NODE_ENV=production like that. (The exception is Bash on Windows,
which uses native Bash.) Similarly, there's a difference in how windows and
POSIX commands utilize environment variables. With POSIX, you use: $ENV_VAR
and on windows you use %ENV_VAR%.
cross-env makes it so you can have a single command without worrying about
setting or using the environment variable properly for the platform. Just set it
like you would if it's running on a POSIX system, and cross-env will take care
of setting it properly.
- Installation
- Usage
- Default Values
cross-envvscross-env-shell- Windows Issues
- Inspiration
- Other Solutions
- Contributors
- LICENSE
This module is distributed via npm which is bundled with node and
should be installed as one of your project's devDependencies:
npm install --save-dev cross-env
WARNING! Make sure that when you're installing packages that you spell things correctly to avoid mistakenly installing malware
NOTE : Version 6 of cross-env only supports Node.js 8 and higher, to use it on Node.js 7 or lower install version 5
npm install --save-dev cross-env@5
I use this in my npm scripts:
{
"scripts": {
"build": "cross-env NODE_ENV=production webpack --config build/webpack.config.js"
}
}Ultimately, the command that is executed (using cross-spawn)
is:
webpack --config build/webpack.config.js
The NODE_ENV environment variable will be set by cross-env
You can also split a command into several ones, or separate the environment variables declaration from the actual command execution. You can do it this way:
{
"scripts": {
"parentScript": "cross-env GREET=\"Joe\" npm run childScript",
"childScript": "cross-env-shell \"echo Hello $GREET\""
}
}Where childScript holds the actual command to execute and parentScript sets
the environment variables to use. Then instead of run the childScript you run
the parent. This is quite useful for launching the same command with different
env variables or when the environment variables are too long to have everything
in one line. It also means that you can use $GREET env var syntax even on
Windows which would usually require it to be %GREET%.
If you precede a dollar sign with an odd number of backslashes the expression
statement will not be replaced. Note that this means backslashes after the JSON
string escaping took place. "FOO=\\$BAR" will not be replaced.
"FOO=\\\\$BAR" will be replaced though.
Lastly, if you want to pass a JSON string (e.g., when using ts-loader), you can do as follows:
{
"scripts": {
"test": "cross-env TS_NODE_COMPILER_OPTIONS={\\\"module\\\":\\\"commonjs\\\"} node some_file.test.ts"
}
}Pay special attention to the triple backslash (\\\) before the
double quotes (") and the absence of single quotes ('). Both of
these conditions have to be met in order to work both on Windows and UNIX.
Note: ${PWD} and $PWD substitute for the current working directory.
To reference an environment variable and provide a default value if that variable is empty or not-defined, use the syntax:
${ENV_VAR_NAME:-default value}Also supports recursive replacement in the default value allowing you to test multiple environment variables before showing a default
# Value of FIRST_VAR_TO_TEST or SECOND_VAR_TO_TEST environment variable if blank or undefined.
# If both are blank or undefined, replace with an empty string
${FIRST_VAR_TO_TEST:-$SECOND_VAR_TO_TEST}Can nest as many as you want
# Value of FIRST_VAR_TO_TEST, then SECOND_VAR_TO_TEST then THIRD_VAR_TO_TEST environment variables.
# If all are blank or undefined, the string "default value if all are empty or undefined"
${FIRST_VAR_TO_TEST:-${SECOND_VAR_TO_TEST:-${THIRD_VAR_TO_TEST:-default value if all are empty or undefined}}}Or even use multiple environment variables in the default values
${NODE_DEBUG_OPTIONS:---inspect=$NODE_DEBUG_PORT $NODE_DEFAULT_OPTIONS}This follows the UNIX standard for environment variables and works for both
cross-env and cross-env-shell.
The cross-env module exposes two bins: cross-env and cross-env-shell. The
first one executes commands using cross-spawn, while the second
one uses the shell option from Node's spawn.
The main use case for cross-env-shell is when you need an environment variable
to be set across an entire inline shell script, rather than just one command.
For example, if you want to have the environment variable apply to several
commands in series then you will need to wrap those in quotes and use
cross-env-shell instead of cross-env.
{
"scripts": {
"greet": "cross-env-shell GREETING=Hi NAME=Joe \"echo $GREETING && echo $NAME\""
}
}The rule of thumb is: if you want to pass to cross-env a command that contains
special shell characters that you want interpreted, then use
cross-env-shell. Otherwise stick to cross-env.
On Windows you need to use cross-env-shell, if you want to handle
signal events
inside of your program. A common case for that is when you want to capture a
SIGINT event invoked by pressing Ctrl + C on the command-line interface.
Please note that npm uses cmd by default and that doesn't support command
substitution, so if you want to leverage that, then you need to update your
.npmrc to set the script-shell to powershell.
Learn more here.
I originally created this to solve a problem I was having with my npm scripts in angular-formly. This made contributing to the project much easier for Windows users.
env-cmd- Reads environment variables from a file instead
Thanks goes to these people (emoji key):
This project follows the all-contributors specification. Contributions of any kind welcome!
Note: this was added late into the project. If you've contributed to this project in any way, please make a pull request to add yourself to the list by following the instructions in the
CONTRIBUTING.md
MIT