npm global install unable to find module

Lrwxrwxrwx 1 root root 40 Jan 7 13:53 /usr/bin/newman -> ls -ltr /usr/lib/node_modules/newman/ That npm config node npm newman which which which ls -ltr /usr/bin/newman Wouldn’t that create another local node_modules directory? And why is So my question is why would the npm install –S be required in Visual studio.

And I can see that the install worked on the WSL command line. I ran s udo npm install -g newman on the WSL command line (debian distro). The –g option should make the package available for all directories for that user, correct? When I install node in WSL Visual Studio is aware of it. Several of the documentation links on npm mentioned installing any package you would use as a command with the –g option. How to share the newman which I installed in the distro with visual studio and why the currently installed one does not get recognized. I am confused as to what the steps should have been when using a combination of WSL, debian linux distro, Node, Visual Studio, and Newman. Thanks for bearing with me on all the questions. By doing that I am hoping to avoid the issues I have been running into with the reporters not being found. The environment set up so that it can be consistently repeated by myself and others in the future. For that reason I am trying to log in detail I am a Newbie to nodejs, npm, wsl and visual studio (about 4 months of sporadic use).

Npm global install unable to find module