kill-others will kill the other processes running if one process dies. Let's look at an example: "start" : "concurrently -names 'SERVER,CLIENT' -prefix-colors 'yellow,blue' -kill-others 'json-server data.json' 'react-scripts start'" And it will give you more organized console output.
It will clean up the processes automatically if they die. There is a npm package which solves this though: concurrently.Ĭoncurrently allows for better process handling. or, a background process could die and you might not notice bc the exit message got buried somewhere in the logs.you’d have to kill the background processes manually to fix this.if you try to run the script again, another background process will be created -> they will interfere with each other or cause the script to fail entirely (i.e.- port conflict).it will still write to stdout and clutter the shell prompt.the background process will keep occupying resources.The background process will keep running which potentially raises some problems: Now, if you need to run multiple commands at the same time - it doesn't matter what order they run in - the simplest way to achieve that would be to use a single ampersand between your commands.īut that presents a number of issues, the biggest being that we don't get good process handling.įor example, imagine the second command/process to run dies. In your package.json file, it would look like this: "scripts" : Īnd the output would look like: > node index.js & echo 'complete!' If you have commands that need to run in order, then using a double ampersand - & - in between those commands will make it so that the preceding command must finish before the next can start.įor simple demo purposes, imagine you have an index.js file that just logs starting and you want to log complete! after it's finished. (and these will work for yarn as well) Sequentially We'll look at two ways of running more than one command as part of a npm script: sequentially and concurrently. Rather than needing to have multiple scripts run, in multiple terminal/shell tabs, and having to remember the order in which to run them, it can be much easier. So is there actually a way to run more than one command? Up until now you might have only run one command per script - often npm start just does something like node server.js. A common scenario: as part of your npm start script, you need to have more than one command run (like webpack -config and webpack -config ).
0 kommentar(er)
