chore(deps): update dependency npm-run-all to v4 #71
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Coming soon: The Renovate bot (GitHub App) will be renamed to Mend. PRs from Renovate will soon appear from 'Mend'. Learn more here.
This PR contains the following updates:
~3.1.2
->~4.1.0
Release Notes
mysticatea/npm-run-all (npm-run-all)
v4.1.5
Compare Source
🐛 Bug fixes
52eaf86...1b41ac5
switchedps-tree
package topidtree
package for security reason.v4.1.4
Compare Source
v4.1.3
Compare Source
🐛 Bug fixes
d56c268
improved label colors35f86ae
fixed a bug that the script name which starts with!
makesnpm-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 onnpm-run-all
command.528d105...43a6b16
fixed the problem with usingyarn
(#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 thatnpm-run-all
showsMaxListenersExceededWarning
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 ofnpm_execpath
on Mac/Linux (#84).Thank you, @bmarcaur !
v4.0.0
Compare Source
🎍 A happy new year! 🎍
Breaking changes
npm
. Before, it was usingnpm
command which is in environment variablePATH
. Now, it uses the path of environment variableNPM_EXECPATH
. If theNPM_EXECPATH
is not defined, it uses the old way.The
NPM_EXECPATH
is set by npm innpm run-script
command. This implies thatnpm-run-all
usesnpm
which is running itself to run tasks.yarn
.yarn run
set theNPM_EXECPATH
as similar tonpm run-script
.Features
--max-parallel
option. You can limit the number of parallelism by this option.--npm-path
option. You can specify the path ofnpm
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
Configuration
📅 Schedule: 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.
This PR was generated by Mend Renovate. View the repository job log.