I think this change was incorrect: npm#2024

The point of this example is that the same script is being used for two different stages (`install` and `post-install`) so it would be a good idea to look at the `npm_lifecycle_event` environment variable inside this script to determine which stage is being run.

PR-URL: npm#3282
Credit: @KevinFCormier
Close: npm#3282
Reviewed-by: @wraithgar

Change the output in `npm ls` for symlink dependencies (including
workspaces) to show the relative path from the project root, rather than
the absolute path of the link target.

This makes the output much less noisy and more ergonomic when many
workspaces and link dependencies are in use, especially when paths are
long.

It is arguable that this output might be slightly misleading, since the
_actual_ workspace symlink from `${root}/node_modules/b` to
`${root}/packages/b` has a link value of `../packages/b`, not just
`packages/b`.  (Or on Windows, always the full absolute path, because
junctions.)  Thus, `npm ls b` will not show the same output as `ls -l
node_modules/b`.

However, `npm ls` shows the logical tree, not the physical tree, so
presenting the user with a path that they can use and interpret is more
important than presenting them with the strictly accurate details of
their filesystem.

PR-URL: npm#3272
Credit: @isaacs
Close: npm#3272
Reviewed-by: @darcyclarke

 * fix(exit-code): account for null auditLevel default (npm#46)

PR-URL: npm#3304
Credit: @NariyasuHeseri
Close: npm#3304
Reviewed-by: @wraithgar

PR-URL: npm#3307
Credit: @rethab
Close: npm#3307
Reviewed-by: @wraithgar

When running 'npm audit', we properly exited correctly with the
appropriate exitCode based on the audit level config and the report
results.

However, when going through the reifyFinish() function (as we do for
'npm audit fix'), we were not setting that properly if the auditLevel
was not set.

Furthermore, if the auditLevel WAS set, we were setting the exit code to
non-zero for *other* reify commands (install, update, etc.), where the
audit information should be strictly advisory.

When --json and --loglevel=silent were set, the exitCode was never being
set properly.

This fixes all these problems.

PR-URL: npm#3311
Credit: @isaacs
Close: npm#3311
Reviewed-by: @wraithgar

PR-URL: npm#3312
Credit: @isaacs
Close: npm#3312
Reviewed-by: @wraithgar

PR-URL: npm#3313
Credit: @spencerwilson
Close: npm#3313
Reviewed-by: @wraithgar