This is already part of the published npm, just not in git

  * fix: bin script path

The did-you-mean code was trying to parse a local package.json to
suggest scripts and bins, which was causing an exception if you ran npm
outside of a directory with a valid package.json.

This fixes that.

PR-URL: #3747
Credit: @wraithgar
Close: #3747
Reviewed-by: @nlf

Before, `npm view npm@^6` would incorrectly report “published over a
year from now” for every entry.  Now it reports the correct dates.

PR-URL: #3739
Credit: @andersk
Close: #3739
Reviewed-by: @wraithgar

The install script will gracefully fail if things don't work.  This is
especially important for versions of npm that won't work in your current
node version.

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

PR-URL: #3753
Credit: @shadowspawn
Close: #3753
Reviewed-by: @wraithgar

The way we were flattening user-agent back into itself meant that any
values that were dependent on other config items would never be seen,
since we have to re-flatten the item for each one it depends on.

We also weren't re-flattening the user-agent when setting workspaces or
workspace, which were things that affected the final result.

This does change the main config value of `user-agent` but not the
flattened one.  We are not using the main config value anywhere (which
is correct).

PR-URL: #3754
Credit: @wraithgar
Close: #3754
Reviewed-by: @nlf

PR-URL: #3738
Credit: @AyushRawal
Close: #3738
Reviewed-by: @wraithgar

See npm/documentation#36

PR-URL: #3759
Credit: @nategreen
Close: #3759
Reviewed-by: @wraithgar

PR-URL: #3760
Credit: @yacoman89
Close: #3760
Reviewed-by: @wraithgar

  * fix: re-emit 'error' event if missed and new listener added
  * fix: do not blow up if process is missing

PR-URL: #3761
Credit: @wraithgar
Close: #3761
Reviewed-by: @lukekarrys