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
This is fine for longer tasks but feels very clumsy for short tasks.
A downside (especially for large projects) is a very large and unreadable npm scripts.
It would be great if a call like npm-run-all \"eslint src/**/*.js\" webpack would just work (where eslint is a binary and webpack a command defined in package json scripts).
The text was updated successfully, but these errors were encountered:
Don't know if #10 is still on the roadmap but I see that Concurrently uses a prefix (npm:) for npm scripts. Then again, I can easily see this working without prefix by indexing npm script keys and an includes conditional.
Not having prefix every command with
npm run
is very convenient but it does force you do alias every command for use innpm-run-all
.For example the following script:
would resolve to the following with npm-run-all:
This is fine for longer tasks but feels very clumsy for short tasks.
A downside (especially for large projects) is a very large and unreadable npm scripts.
It would be great if a call like
npm-run-all \"eslint src/**/*.js\" webpack
would just work (where eslint is a binary and webpack a command defined in package json scripts).The text was updated successfully, but these errors were encountered: