search

mysticatea / npm-run-all

A CLI tool to run multiple npm-scripts in parallel or sequential.
MIT License
5.72k stars 240 forks source link

[BUG] nodemon v2.0.6 not working with npm-run-all --parallel in nodejs v14.15.1 LTS #194

Open danny007in opened 3 years ago

danny007in commented 3 years ago

Follow link please https://github.com/remy/nodemon/issues/1808

Janaka-Steph commented 3 years ago

I have a similar issue with parcel, watch:popup and watch:background work when run independently, but not when run together with run-p.

 "watch": "yarn run clean && yarn run copy-assets && run-p watch:**",
 "watch:popup": "parcel watch src/popup.html --public-url='/'",
 "watch:background": "parcel watch scripts/background.ts",

The funny thing is that yarn run watch crashes, but npm run watch works fine!

danny007in commented 3 years ago

I have a similar issue with parcel, watch:popup and watch:background work when run independently, but not when run together with run-p.

 "watch": "yarn run clean && yarn run copy-assets && run-p watch:**",
 "watch:popup": "parcel watch src/popup.html --public-url='/'",
 "watch:background": "parcel watch scripts/background.ts",

The funny thing is that yarn run watch crashes, but npm run watch works fine!

In this scenario we are using npm run

danny007in commented 3 years ago

I have a similar issue with parcel, watch:popup and watch:background work when run independently, but not when run together with run-p.

 "watch": "yarn run clean && yarn run copy-assets && run-p watch:**",
 "watch:popup": "parcel watch src/popup.html --public-url='/'",
 "watch:background": "parcel watch scripts/background.ts",

The funny thing is that yarn run watch crashes, but npm run watch works fine!

But working fine After using this https://www.npmjs.com/package/concurrently working

danny007in commented 3 years ago

@Janaka-Steph checkout https://github.com/ColorlibHQ/AdminLTE/pull/3334

danny007in commented 3 years ago

Actually not working in windows 10 only with nodejs 14

danny007in commented 1 year ago

issue is still not solved