You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -97,6 +97,7 @@ Check out documentation and other usage examples in the [`docs` directory](./doc
97
97
- `options` (optional): an object containing any of the below:
98
98
- `cwd`: the working directory to be used by all commands. Can be overridden per command.
99
99
Default: `process.cwd()`.
100
+
- `shell`: shell executable used to run command strings. When unset, uses `npm_config_script_shell` if present (for example when run via `npm run`), otherwise `cmd.exe` on Windows or `/bin/sh` elsewhere. See [shell resolution](./docs/shell-resolution.md).
100
101
- `defaultInputTarget`: the default input target when reading from `inputStream`.
101
102
Default: `0`.
102
103
- `handleInput`: when `true`, reads input from `process.stdin`.
Each command runs inside a shell, not as a bare executable.
4
+
By default, concurrently uses `cmd.exe` on Windows and `/bin/sh` elsewhere.
5
+
6
+
## Using a different shell
7
+
8
+
If the default shell isn't suitable, it's possible to instruct concurrently to use a specific shell in a few ways.
9
+
10
+
This is useful, for example, to use Unix-style syntax (for example `BROWSER=none npm start`) on Windows, if you set concurrently shell to e.g. Git Bash.
11
+
12
+
### Via explicit override
13
+
14
+
An explicit shell override takes precedence over every other configuration.
0 commit comments