chore(deps): update dependency npm-run-all to v4

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
npm-run-all	~3.1.2 → ~4.1.0

---

Release Notes

mysticatea/npm-run-all (npm-run-all)

v4.1.5

Compare Source

🐛 Bug fixes

• 52eaf86...1b41ac5 switched ps-tree package to pidtree package for security reason.

v4.1.4

Compare Source

v4.1.3

Compare Source

🐛 Bug fixes

• d56c268 improved label colors
• 35f86ae fixed a bug that the script name which starts with ! makes npm-run-all confusing.

v4.1.2

Compare Source

Bug fixes

• 096779b fixed the problem that --aggregate-output option does not work if child tasks print large output (#​111). Thank you, @​jlopezxs!
• 693261b fixed the problem that --aggregate-output option does not work on npm-run-all command.
• 528d105...43a6b16 fixed the problem with using yarn (#​113).

v4.1.1

Compare Source

Bug fixes

• fbd4024 fixed a regression bug of --print-name.

v4.1.0

Compare Source

Features

• e07e782 add --aggregate-output option. This option avoids that the output of tasks is mixed even if parallel mode. Don't use this option if a task never finishes (e.g. web server, file watching, ...).
  Thank you, @​fatso83 !

Bug fixes

• f7f7b43 fixed a bug that npm-run-all shows MaxListenersExceededWarning warnings if it runs many tasks in parallel.

v4.0.2

Compare Source

Bug fixes

• b90575b fixed unintentional failing of the assertion check about --race option. If there is a mix of --parallel and --serial then --race option had failed always. (fixes #​88).

v4.0.1

Compare Source

Bug fixes

• bb9e627 fixed the problem of npm_execpath on Mac/Linux (#​84).
  Thank you, @​bmarcaur !

v4.0.0

Compare Source

🎍 A happy new year! 🎍

Breaking changes

• It dropped supports for Node 0.10, 0.12. See also: https://github.com/nodejs/LTS
• It changed the way which finds the path of npm. Before, it was using npm command which is in environment variable PATH. Now, it uses the path of environment variable NPM_EXECPATH. If the NPM_EXECPATH is not defined, it uses the old way.
  The NPM_EXECPATH is set by npm in npm run-script command. This implies that npm-run-all uses npm which is running itself to run tasks.
  • It supports yarn. yarn run set the NPM_EXECPATH as similar to npm run-script.

Features

• It added --max-parallel option. You can limit the number of parallelism by this option.
• It added --npm-path option. You can specify the path of npm by this option. For example, npm-run-all foo --npm-path npm keeps the old behavior.
• d7821df added colors for --print-label option. Thank you, @​nulltask !

Chore

• It no longer uses babel to transpile.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	npm-run-all@​3.1.2 ⏵ 4.1.5			+2

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: npm braces is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: yarn.lock → npm/nyc@11.9.0 → npm/braces@2.3.2 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/braces@2.3.2. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report