-
-
Notifications
You must be signed in to change notification settings - Fork 242
Issues: mysticatea/npm-run-all
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Feature request: --continue-on-error, BUT it returns a failing error code if any command fails
#223
opened Jan 12, 2022 by
DanKaplanSES
Getting "Error: Cannot find module" when running basic setup
#218
opened Nov 19, 2021 by
kennyjwilli
CVE-2021-42740 (Critical vulnerability) on shell-quote (dependency package)
#217
opened Nov 11, 2021 by
Rashmi-nw
Usage of npm-run-all cli params --sequential and --parallel at the same time
#213
opened Aug 26, 2021 by
rcampbel
Why is npm-run-all so narcissistic about the config field in package.json.
#212
opened Aug 15, 2021 by
airtonix
Broken with npm@7 when using npx ("Need to install the following packages: run")
#209
opened May 4, 2021 by
Domiii
Glob matching does not work when specified in script using Yarn 2
#200
opened Feb 20, 2021 by
Robin-Hoodie
[BUG] nodemon v2.0.6 not working with npm-run-all --parallel in nodejs v14.15.1 LTS
#194
opened Dec 10, 2020 by
danny007in
ProTip!
Type g i on any issue or pull request to go back to the issue listing page.