nativescript cli isnt identified after instalation.

[Betryx]

Issue Description

when i try running ns <command> as an example ns create patron --js or any other command of the nativescript cli,
i get an error message that says ns isnt identified:

Output:
ns: The term 'ns' is not recognized as a name of a cmdlet, function, script file, or executable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try again.

Reproduction

No response

Relevant log output (if applicable)

Output:
     `ns: The term 'ns' is not recognized as a name of a cmdlet, function, script file, or executable 
      program.
      Check the spelling of the name, or if a path was included, verify that the path is correct and try 
       again.`

Environment

No response

Please accept these terms

• I have searched the existing issues as well as StackOverflow and this has not been posted before
• This is a bug report
• I agree to follow this project's Code of Conduct

[rigor789]

Make sure you have installed everything as noted in the setup guide

https://docs.nativescript.org/environment-setup.html#windows-android

[Betryx]

everything is installed as it should be via the guide, but still doesnt work

[rigor789]

Is your npm set up correctly? The global install dir should be in your Environment Variables/Path - can't really give exact steps to fix as it depends on the way you installed nodejs.

[Betryx]

yes my npm is installed corectly.

[rigor789]

Ok, so npm is good, run npm -g prefix and make sure that path + /bin is in your PATH variable.

For example:

$ npm -g prefix

/Users/rigor789/.nvm/versions/node/v18.3.0

So I have

/Users/rigor789/.nvm/versions/node/v18.3.0/bin

in my PATH.

(my example is from a macos machine, but the only difference would be the actual path).

Once you are certain the path is in your system PATH (environment variable), then restart your terminal to pick up the environment changes, and see if ns -v works.

And just to add, this has nothing to do with ns specifically, it's a standard globally installed node module which you are having trouble with - adding this just to help with your search.

[anterof5]

Worked for me: https://stackoverflow.com/questions/44958847/message-the-term-ng-is-not-recognized-as-the-name-of-a-cmdlet