Note this started failing after the recent npm changes. I'll try getting it passing again but let me know if there's any feedback on what's here so far...

Ok I've updated this PR to significantly less changes then previously...

• each test run uses an isolated folder for the global installations, that global npm bin dir is added to the PATH
• each test run uses only an empty npmrc and prevents the use of ~/.npmrc and the global one
• those are both configured via environment variables, those variables must be propagated to child node processes (e2e tests, npm installs etc)

This no longer removes --global or changes how npm/yarn versions are determined like it original did.

This does NOT prevent the use of the shared global npm database (~/.npm/_cacache/ configured via NPM_CONFIG_CACHE env var) unlike the npm global modules which are isolated. So despite the installed global modules being isolated they shouldn't have to be re-downloaded if the global database is populated. This might change once bazel is used because the bazel test process doesn't have write permission to that global database.

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}