Explain/give "why" reasons, for operations done while installing a package

[claytoneast]

I'd like to apologize in advance if what I'm requesting is already in a CLI flag that I didn't properly read/explore.

I'd like to know why the things that happen when I run npm install some_package, are happening.

The Problem (with an example)

Current behavior example:

npm install --save uuid

added 2 packages, removed 2 packages, changed 3 packages, and audited 1297 packages in 7s

This command output leaves something to be desired. I asked for a single package with no dependencies to be installed. Apparently, 2 packages have been added, 2 have been removed, and 3 others have been changed.

Why were two packages added when I asked for one to be added, which I know for a fact has no dependencies? What other package (that I didn't ask for) was added? What 2 packages were removed, and why did they leave? Why were 3 others changed, and what packages were they? Why are 1297 packages being audited?

Potential solution

Let's use the same example that we did above. npm install --save uuid. Here is an example of what I'd like to see when running this command.

npm install --save uuid

Added 2 packages.
Added uuid, since it is the package you requested to be installed.
Added some other package for some reason (I, the writer of this proposal/plea-for-help, have no idea what this package is or why it was added, since I didn't ask for it, but there must be a reason for it.)

Removed 2 packages.
Removed node_modules/sequelize/node_modules/uuid, since it was version 3.4 and you are currently installing version 3.4 in the root node_modules (dedupe operation).
Removed node_modules/devtools/node_modules/uuid, since it was version 3.4 and you are currently installing version 3.4 in the root node_modules (dedupe operation).

Changed 3 packages.
Changed some_package1 package for some reason
Changed some_package2 package for some reason
Changed some_package3 package for some reason

Audited 1297 packages
Audited these packages in order to do whatever it is we needed to do (Again, no idea what this message should be as I don't know what it's doing :( )

I've run npm install somepackage with the --verbose flag, and it seems to only give me more information of the "what" variety. In my experience, "what" information is not helpful without the "why" information. I think it would be great if npm install a_specific_package gave concise "why" information.

Thanks for your time.