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.
Background
This package does not currently support sorting the
scripts
field of apackage.json
whennpm-run-all
is a devDependency, regardless of how it is actually used in the scripts.While there is certainly a place for refraining from sorting the scripts when
npm-run-all
is used for running scripts sequentially (e.g.npm-run-all --serial
), there are use cases where the user may wish for the scripts to be sorted even whennpm-run-all
is a devDepenency (e.g.npm-run-all -p
). This concern has been raised in previous PRs and issues (see this PR and this issue).This PR enables this behavior.
Changes
The following uses of
npm-run-all
will continue to NOT sort thescripts
:npm-run-all
npm-run-all --serial
npm-run-all --sequential
npm-run-all -s
run-s
While the following uses now WILL sort the
scripts
:npm-run-all --parallel
run-p