Gar

Something that was talked about in previous discussions about this was having some way to at least give people a fighting chance of making this an iterative change. Namely, that...

This realistically would end up needing to be a separate config item telling config which values to revert back to their defaults, since `--registry` is already a string so we...

It already is the default. I believe if there were a way to *delete* a config entry this would functionally do the same thing?

But that may not work because you really would want to be able to do that on the cli. What this really does need is a new config item that...

`:is(:type(git,remote))` would give you everything in your tree that is a git or remote reference.

This seems like a pretty significant security concern. If I clone a repo and run `npm install` it'll run any node.exe that happens to be in there? Also, this decision...

Ok yes that kind of thing was what was explicitly not supported, for reasons stated previously. If something else runs node it has no way of knowing that you started...

If you need some other node.exe to take precedence, you should prepend the directory it lives in to your `PATH` environment variable. Even if you scope this to your current...

The security risk was in running `node.exe` from the cwd, which is not what you are suggesting. The binary version of node.js is fully functional, but it has to be...

That's why you use `set` instead of `setx`. `set` only changes it for the current shell context, not globally.