additionalArguments: list of additional arguments passed that will get replaced in each command.Tips to Perfectly Uninstall Parallels Desktop on Mac OS X.restartDelay: how many milliseconds to wait between process restarts.restartTries: how many attempts to restart a process that dies will be made.If first, only the first process to exit will make up the success of the run if last, the last process that exits will determine whether the run succeeds.Īnything else means all processes should exit successfully. successCondition: the condition to consider the run was successful.raw: whether raw mode should be used, meaning strictly process output willīe logged, without any prefixes, coloring or extra stuff.prefixLength: how many characters to show when prefixing with command.Prefix colors specified per-command take precedence over this list. If concurrently would run more commands than there are colors, the last color is repeated, unless if the last color value is auto which means following colors are automatically picked to vary. prefixColors: a list of colors as supported by chalk or auto for an automatically picked color."command-]).ĭefault: the name of the process, or its index if no name is set. s, -success Which command(s) must exit with code 0 in orderįor concurrently exit with code 0 too. n "styles|scripts|server" -name-separator "|" name-separator The character to split on. n, -names List of custom names to be used in prefixĮxample names: "main,browser,server" New processes only spawn after all restart tries m, -max-processes How many processes should run at once.Įxact number or a percent of CPUs available (for example "50%"). # Running only lint:js and lint:ts # with lint:fix:js and lint:fix:ts excluded Remember to surround separate commands with quotes:
The tool is written in Node.js, but you can use it to run any commands. The concurrently command is now also available under the shorthand alias conc.
Please change this flag if this doesn't apply in your case. * It's recommended to add concurrently as devDependencies as it's usually used for developing purposes. With -kill-others switch, all commands are killed if one diesĬoncurrently can be installed in the global scope (if you'd like to have it available and use it on the whole system) or locally for a specific package (for example if you'd like to use it in the scripts section of your package):.Tired of opening terminals and made concurrently. Also if one process fails, others still keep runningĪnd you won't even notice the difference.Īnother option would be to just run all commands in separate terminals. Like npm run watch-js & npm run watch-less but better.īut the usual way to run multiple commands concurrently is
0 kommentar(er)
