Allow built-in install task

[hugojosefson]

Wow! What a nice, well-structured repo and tool you have here!

I want to be able to have a run-script "install-sub-dependencies": "cd sub/ && run-s install", which does npm install or yarn install to install the dependencies in the sub/ project, depending on how the main script was called.

This PR enables the install task, which is run without "run" before it.

[codecov-io]

Codecov Report

Merging #110 into master will decrease coverage by 0.93%. The diff coverage is 87.5%.

@@            Coverage Diff             @@
##           master     #110      +/-   ##
==========================================
- Coverage   92.88%   91.95%   -0.94%     
==========================================
  Files          22       22              
  Lines         464      460       -4     
==========================================
- Hits          431      423       -8     
- Misses         33       37       +4

Impacted Files	Coverage Δ
lib/match-tasks.js	100% <100%> (ø)	:arrow_up:
lib/run-task.js	83.87% <80%> (-3.63%)	:arrow_down:
bin/common/parse-cli-args.js	90.8% <0%> (-2.46%)	:arrow_down:
lib/index.js	93.58% <0%> (-0.17%)	:arrow_down:
lib/run-tasks.js	85.07% <0%> (ø)	:arrow_up:
bin/npm-run-all/help.js	100% <0%> (ø)	:arrow_up:
bin/npm-run-all/main.js	100% <0%> (ø)	:arrow_up:

---

Continue to review full report at Codecov.

Legend - Click here to learn more Δ = absolute <relative> (impact), ø = not affected, ? = missing data Powered by Codecov. Last update 43a6b16...f6d5b74. Read the comment docs.

[mysticatea]

Thank you for this PR.

However, because of npm has a ton of commands, I don't think that npm-run-all should handle only npm install as special.

I think that this is out of scope because npm-run-all is a tool to do npm run command with multiple tasks, but I can accept if there is a proper way to specify commands except run. The way should be that users can distinguish between npm run and other commands easily.

[hugojosefson]

Thank you @mysticatea so much for your feedback!

That's a good idea to make sure the user knows what they are doing.

I was also thinking that npm-run-all is very good at choosing yarn or npm, depending on how it was initially run. So it could be quite useful to be able to run commands too, if the commands are the same in npm and yarn.

Previously, I thought install was the only command that was the same and did the same thing in both npm and yarn, but now I see that for example publish is also the same command. I agree that it should be possible to distinguish between commands and run-scripts.

How about using for example command: as a prefix for commands, such as for example:

{
  "scripts": {
    "install-sub-dependencies": "cd sub && run-s clean command:install"
  }
}

Or maybe even better by for example adding a specific argument to specify a command:

{
  "scripts": {
    "install-sub-dependencies": "cd sub && run-s clean --command install"
  }
}

Would that be a good way forward?

Thanks for the consideration! /Hugo

[mysticatea]

I apology that I'm late to respond.

About the command:install looks, I'm afraid because it runs npm run command:install currently. npm-run-all recommends to use : as separators (Glob-like pattern matching for script names).

The --command install looks nice to me, but it's long a bit. Hmm, how about :install? It's still a breaking change, but it's shorter and distinguishable. I can image absolute path to specify outside of run command from the :install syntax.