Question 1

How do I set multiple environment variables with cross-env?

Accepted Answer

You can set multiple variables in a single command, e.g., `cross-env FIRST_ENV=one SECOND_ENV=two node script.js`. This is demonstrated in the README, allowing for cleaner and more efficient npm scripts without platform issues.

Question 2

cross-env vs env-cmd: which one should I use for .env files?

Accepted Answer

cross-env sets variables inline in scripts, while env-cmd reads from .env files. If you need file-based environment management, env-cmd is better; cross-env is ideal for simple, script-level variable setting across platforms.

Question 3

How to pass a JSON string in cross-env for tools like ts-loader?

Accepted Answer

Use triple backslashes before double quotes, e.g., `TS_NODE_COMPILER_OPTIONS={\"module\":\"commonjs\"}`. The README specifies this syntax to ensure compatibility on both Windows and UNIX, though it can be tricky to get right.

Question 4

Why is my cross-env script not working on Windows?

Accepted Answer

Ensure you're using cross-env-shell for commands with shell characters or signal events. Also, check npm's script-shell setting if using command substitution, as noted in the Windows Issues section of the README.

Question 5

When should I use cross-env-shell instead of cross-env?

Accepted Answer

Use cross-env-shell when you need environment variables to persist across multiple commands in an inline shell script or to handle signal events like Ctrl+C on Windows. For single commands, cross-env is usually sufficient.

Question 6

Can I use cross-env outside of npm scripts?

Accepted Answer

cross-env is primarily designed for npm scripts; using it in general shell scripts or other environments might require extra setup and isn't directly supported, so alternative tools may be more appropriate.

cross-env

What is cross-env?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions