I think this change is ridiculous, and enable-pre-post-scripts must be true by default. Runs only on local pnpm install.. How will the users know about the potential consequences without the warning? We run npm commands a lot. They may however be other users coming from the yarn convenience, stumbling over this. no, the standard lifecycle scripts like postinstall or prepublishOnly are not affected. npm run dev Hey, you've made it this far! The scripts field holds an object where you can specify various commands and scripts you want to expose. I would require them to wait for each other to finish, these will fire off sequentially but won't wait. Posted on Aug 9, 2020 So the run command's own flags would have to be before the script's name. Per the, While this seems like an elegant solution at first, checking out the dependency tree of, I think that, if you have a lot of scripts to run, and you are using Package.json as a Task Runner (like, this doesn't work, as indicated in the question: "When I use pre/post fixing they launch sequentially but they don't wait for the parent script to finish before executing.". As you may need to add more and more to this scripts it will become messy and harder to use. From my side: I don't want a yarn clone. Use concurrently to run the commands in parallel with a shared output stream. Webpack compiler provides hooks to intercept compilation. This is why, I implement my own lib, run-screen. The bugs in concurrently mentioned by @StijndeWitt have now been fixed in, @StijndeWitt parallelshell has been deprecated in favor of npm-run-all. When you run your concurrently command you should see in your terminal that all your watch scripts are running in parallel. Well put, @aparajita! It's because these instances both open automatically while you run only 1 statement, which is your initial goal. Irecommendadding somesortofdetection forcases wherecmdmatches ascriptname inpackage.json andtosuggestusing pnpmrun