We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
It would be convenient to have a shorthand for npm run my-script, like concurrently has:
npm run my-script
concurrently
concurrently "npm:watch-js" "npm:watch-css" "npm:watch-node"
I think the npm:script syntax is good as-is.
npm:script
concurrently also supports wild cards and negations. matcher could possibly be used for this:
matcher
concurrently "npm:lint:*(!fix)"
The text was updated successfully, but these errors were encountered:
This should also support resolving pre- and post- scripts.
pre-
post-
Ideally, this would parse all commands in order and make a task for each of them.
Sorry, something went wrong.
If the task is unnamed, the name should come from the script:
> listr yarn:lint tests::pnpm:test 'npm:build-*' ⠼ lint ◼ tests ◼ build-ts ◼ build-scss ◼ postbuild
The documentation should also mention quoting globs to escape them.
concurrently references: expand-npm-shortcut, expand-npm-wildcard
expand-npm-shortcut
expand-npm-wildcard
Potential matcher blocker: sindresorhus/matcher#35
No branches or pull requests
It would be convenient to have a shorthand for
npm run my-script
, likeconcurrently
has:I think the
npm:script
syntax is good as-is.concurrently
also supports wild cards and negations.matcher
could possibly be used for this:concurrently "npm:lint:*(!fix)"
The text was updated successfully, but these errors were encountered: