Haha, good point. Actually, the installation procedure is not skipped; npm will install the package in the 'dependencies' section; if you're interested, you can look at 'package-lock.json'. However, the issue is whether to make a selection at the package level or as an end-developer persona. IMHO, every non-tightly dependent output dependence should be treated as optional but should make the installation more controlled for end developers.
