You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We would like to use the --print-labels option, but when giving npm-run-all extra arguments (for example npm-run-all --print-labels \"build -- --watch\" [...]), this prints very long labels that add clutter to the output.
With concurrently, we manage this with --names, but that forces us to use both npm-run-all and concurrently, while I would much rather only using npm-run-all.
It would be great if we could either:
Specify a custom label. Not sure what would be the best syntax for it, but I can think of 2 at least:
concurrently-like, so in the example above, that would be:
Or if there was a way to strip extra arguments from the command given (in the example above, that would just be build) but that could be problematic with commands like npm-run-all --print-labels \"build -- --arg1\" \"build -- --arg2\" [...] (though a bit of a niche use case)
The text was updated successfully, but these errors were encountered:
Thank you for this issue. Apology for the slow response.
The concurrently-like option seems nicer. Because npm-run-all allows glob-like patterns to specify task names (e.g. build:\"build:* -- --watch\"), the label can apply to multiple tasks.
We would like to use the
--print-labels
option, but when givingnpm-run-all
extra arguments (for examplenpm-run-all --print-labels \"build -- --watch\" [...]
), this prints very long labels that add clutter to the output.With
concurrently
, we manage this with--names
, but that forces us to use bothnpm-run-all
andconcurrently
, while I would much rather only usingnpm-run-all
.It would be great if we could either:
Specify a custom label. Not sure what would be the best syntax for it, but I can think of 2 at least:
concurrently
-like, so in the example above, that would be:Or if there was a way to strip extra arguments from the command given (in the example above, that would just be
build
) but that could be problematic with commands likenpm-run-all --print-labels \"build -- --arg1\" \"build -- --arg2\" [...]
(though a bit of a niche use case)The text was updated successfully, but these errors were encountered: