Skip to content
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

Custom labels #121

Open
astorije opened this issue Jan 7, 2018 · 2 comments · May be fixed by #167
Open

Custom labels #121

astorije opened this issue Jan 7, 2018 · 2 comments · May be fixed by #167

Comments

@astorije
Copy link

astorije commented Jan 7, 2018

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:
      npm-run-all --print-labels --labels=build,[...] \"build -- --watch\" [...]
    • Some way to prefix commands:
      npm-run-all --print-labels build:\"build -- --watch\" [...]
  • 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)

@mysticatea
Copy link
Owner

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.

@jonaskello
Copy link

Having shorter labels would be really nice. Any progress on this?

@GodLesZ GodLesZ linked a pull request Apr 23, 2019 that will close this issue
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants