Use fs.realpath to handle nvm symlink proxy

[zikaari]

At least on windows (not sure of other platforms), nvm, will use symlink proxying to make things work and look natural.

But since symlink lives somewhere else on file system, __dirname !~= 'C:\Program Files\nodejs...' but more so __dirname ~= 'C:\Users\...\AppData\nvm\v7.0.0\...'

[sindresorhus]

Wouldn't it make more sense to do fs.realPath in https://github.com/sindresorhus/global-dirs instead?

[zikaari]

That was my initial plan as well, but then I dropped it. The primary reason being that use cases of global-dirs are very diverse, furthermore:

1. It'll be most likely a breaking change
2. If a global-dirs consumer needs "actual" path, they can do fs.realpath themselves, however there is no way of going other way around, imagine another consumer who doesn't want the "actual" path of global node_modules but instead the "typical" one (C:\Program Files\nodejs...). Introducing this change will break their expectations of what they'll get.

Also, I think real path of C:\Program Files\nodejs\... is kind of analogous to private API, subject to weird behaviors at any time.

Instead, maybe this situation/caveat can be explained in global-dirs docs.

Also, what exactly is wrong with npm@5.x that's leading to failing tests?

[sindresorhus]

That's a very good point. Thanks for elaborating. I agree.

[sindresorhus]

Also, what exactly is wrong with npm@5.x that's leading to failing tests?

See: yeoman/update-notifier#114 (comment)