concurrently

# Prefixing ## Prefix Styles concurrently will by default prefix each command's outputs with a zero-based index, wrapped in square brackets: ```bash $ concurrently 'echo Hello there' "echo 'General Kenobi!'" [0] Hello there [1] General Kenobi! [0] echo Hello there exited with code 0 [1] echo 'General Kenobi!' exited with code 0 ``` If you've given the commands names, they are used instead: ```bash $ concurrently --names one,two 'echo Hello there' "echo 'General Kenobi!'" [one] Hello there [two] General Kenobi! [one] echo Hello there exited with code 0 [two] echo 'General Kenobi!' exited with code 0 ``` There are other prefix styles available too: | Style | Description | | --------- | --------------------------------- | | `index` | Zero-based command's index | | `name` | The command's name | | `command` | The command's line | | `time` | Time of output | | `pid` | ID of the command's process (PID) | | `none` | No prefix | Any of these can be used by setting the `--prefix`/`-p` flag. For example: ```bash $ concurrently --prefix pid 'echo Hello there' 'echo General Kenobi!' [2222] Hello there [2223] General Kenobi! [2222] echo Hello there exited with code 0 [2223] echo 'General Kenobi!' exited with code 0 ``` It's also possible to have a prefix based on a template. Any of the styles listed above can be used by wrapping it in `{}`. Doing so will also remove the square brackets: ```bash $ concurrently --prefix '{index}-{pid}' 'echo Hello there' 'echo General Kenobi!' 0-2222 Hello there 1-2223 General Kenobi! 0-2222 echo Hello there exited with code 0 1-2223 echo 'General Kenobi!' exited with code 0 ``` ## Prefix Colors By default, concurrently automatically assigns colors to each command's prefix, cycling through `cyan`, `magenta`, `green`, `yellow`, and `blue` (the same palette and order used by turborepo). This can be changed by using the `--prefix-colors`/`-c` flag, which takes a comma-separated list of colors to use.<br/> The available values are color names (e.g. `green`, `magenta`, `gray`, etc), a hex value (such as `#23de43`), `auto` to automatically select a color, or `reset` to disable coloring. ```bash $ concurrently -c red,blue 'echo Hello there' 'echo General Kenobi!' ``` <details> <summary>List of available color names</summary> - `black` - `blue` - `cyan` - `green` - `gray` - `magenta` - `red` - `white` - `yellow` </details> Colors can take modifiers too. Several can be applied at once by appending `.<modifier 1>.<modifier 2>` and so on. ```bash $ concurrently -c '#23de43.inverse,bold.blue.dim' 'echo Hello there' 'echo General Kenobi!' ``` <details> <summary>List of available modifiers</summary> - `reset` - `bold` - `dim` - `hidden` - `inverse` - `italic` - `strikethrough` - `underline` </details> A background color can be set in a similarly fashion. ```bash $ concurrently -c bgGray,red.bgBlack 'echo Hello there' 'echo General Kenobi!' ``` <details> <summary>List of available background color names</summary> - `bgBlack` - `bgBlue` - `bgCyan` - `bgGreen` - `bgGray` - `bgMagenta` - `bgRed` - `bgWhite` - `bgYellow` </details> ### Advanced Color Functions concurrently supports all [Chalk color functions](https://github.com/chalk/chalk#256-and-truecolor-color-support): | Function | Description | | ---------------- | --------------------------- | | `#RRGGBB` | Foreground hex (shorthand) | | `bg#RRGGBB` | Background hex (shorthand) | | `hex(#RRGGBB)` | Foreground hex | | `bgHex(#RRGGBB)` | Background hex | | `rgb(R,G,B)` | Foreground RGB (0-255) | | `bgRgb(R,G,B)` | Background RGB (0-255) | | `ansi256(N)` | Foreground ANSI 256 (0-255) | | `bgAnsi256(N)` | Background ANSI 256 (0-255) | All functions can be chained with colors and modifiers: ```bash # Hex colors $ concurrently -c 'bg#FF0000.bold,black.bgHex(#00FF00).dim' 'echo Red bg' 'echo Green bg' # RGB colors $ concurrently -c 'rgb(255,136,0).bold,black.bgRgb(100,100,255)' 'echo Orange' 'echo Blue bg' # ANSI 256 colors $ concurrently -c 'ansi256(199),ansi256(50).bgAnsi256(17)' 'echo Pink' 'echo Cyan on blue' ``` ### Scoping the Color to Part of a Template By default, the entire prefix is colored. When using a template, you can restrict coloring to a specific region by wrapping it with the `{color}` and `{/color}` markers — anything outside the markers is rendered without color. ```bash $ concurrently -c red,blue --prefix '[{color}{name}{/color}] {pid}' --names one,two 'echo Hello there' 'echo General Kenobi!' ``` In the example above, only `one` and `two` are colored — the surrounding brackets and the PID stay in the terminal's default color. If only one of the markers is present, the missing side is implicit: an `{color}` without a matching `{/color}` colors everything from the opener to the end of the prefix, and a `{/color}` without a preceding `{color}` colors everything from the start of the prefix up to the closer. A template with neither marker is colored in full, matching the previous behavior. ## Prefix Length When using the `command` prefix style, it's possible that it'll be too long.<br/> It can be limited by setting the `--prefix-length`/`-l` flag: ```bash $ concurrently -p command -l 10 'echo Hello there' 'echo General Kenobi!' [echo..here] Hello there [echo..bi!'] General Kenobi! [echo..here] echo Hello there exited with code 0 [echo..bi!'] echo 'General Kenobi!' exited with code 0 ``` It's also possible that some prefixes are too short, and you want all of them to have the same length.<br/> This can be done by setting the `--pad-prefix` flag: ```bash $ concurrently -n foo,barbaz --pad-prefix 'echo Hello there' 'echo General Kenobi!' [foo ] Hello there [foo ] echo Hello there exited with code 0 [barbaz] General Kenobi! [barbaz] echo 'General Kenobi!' exited with code 0 ``` > [!NOTE] > If using the `pid` prefix style in combination with [`--restart-tries`](./restarting.md), the length of the PID might grow, in which case all subsequent lines will match the new length.<br/> > This might happen, for example, if the PID was 99 and it's now 100.