npm ls -g --parseable uses local path, not global

[SBoudrias]

I can reproduce this bug on Windows and on TravisCI (so probably other Unix system), but the behavior seems OK on Mac OSx.

When I run npm ls -g --parseable, the ouput correctly shows the name of global packages, but this name is prefixed with the local node_modules folder path, not the global path.

I'd expect --parseable to return the package real path (the global node_modules).

[sindresorhus]

👍

[busches]

@SBoudrias @sindresorhus are you still seeing this problem on MacOS? npm 3.10.5 is working correctly on Windows.

[npm-robot]

We're closing this issue as it has gone thirty days without activity. In our experience if an issue has gone thirty days without any activity then it's unlikely to be addressed. In the case of bug reports, often the underlying issue will be addressed but finding related issues is quite difficult and often incomplete.

If this was a bug report and it is still relevant then we encourage you to open it again as a new issue. If this was a feature request then you should feel free to open it again, or even better open a PR.

For more information about our new issue aging policies and why we've instituted them please see our blog post.