Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'ncu' is not recognized as an internal or external command, operable program or batch file. #266

Closed
lorenzosjb opened this issue Sep 8, 2016 · 11 comments

Comments

@lorenzosjb
Copy link

lorenzosjb commented Sep 8, 2016

Please include the ncu path to the install process because after installing in Windows 7 without any errors and executing ncu command. This is my output. Thanks for the help.

C:\Users\jimenelo>npm install -g npm-check-updates
C:\Users\jimenelo\AppData\Roaming\npm\ncu -> C:\Users\jimenelo\AppData\Roaming\npm\node_modules\npm-check-updates\bin\ncu
C:\Users\jimenelo\AppData\Roaming\npm\npm-check-updates -> C:\Users\jimenelo\AppData\Roaming\npm\node_modules\npm-check-updates\bin\npm-check-updates
C:\Users\jimenelo\AppData\Roaming\npm
`-- [email protected]

C:\Users\jimenelo>npm -g ls --depth=0
C:\Users\jimenelo\AppData\Roaming\npm
+-- [email protected]
+-- [email protected]
+-- [email protected]
`-- [email protected]

C:\Users\jimenelo>ncu
'ncu' is not recognized as an internal or external command,
operable program or batch file.

@lorenzosjb lorenzosjb reopened this Sep 8, 2016
@raineorshine
Copy link
Owner

Hi, thanks for reporting! A couple questions.

Is npm-check-updates not found as well?
Does the same problem occur for any global npm module, or just ncu?

@arturparkhisenko
Copy link

arturparkhisenko commented Sep 26, 2016

@raineorshine got the same error today, win10pro, node v6.6.0, npm 3.10.3.
Either ncu or npm-check-updates aren't found (global ofc).
npm list -g --depth=0 shows that [email protected] is installed, and i already tried to reinstall it.

Wow.. maybe it's not fault of npm-check-updates, i found that bower and etc not working too).. looking why.
Repaired NodeJS and everything works fine. Thanks)

@raineorshine
Copy link
Owner

Okay, closing :)

@PixelWeaver
Copy link

PixelWeaver commented Jul 22, 2019

@raineorshine got the same error today, win10pro, node v6.6.0, npm 3.10.3.
Either ncu or npm-check-updates aren't found (global ofc).
npm list -g --depth=0 shows that [email protected] is installed, and i already tried to reinstall it.

Wow.. maybe it's not fault of npm-check-updates, i found that bower and etc not working too).. looking why.
Repaired NodeJS and everything works fine. Thanks)

What do you mean by repairing NodeJS ? Did you uninstall/reinstall ?

@arturparkhisenko
Copy link

arturparkhisenko commented Jul 22, 2019

@PixelWeaver I've found I had multiple NodeJS versions and I suppose it was required to switch from one to another after a brew update. And maybe one of the second issues I have found was that in my shell config file (ex.: .zshrc) I did the wrong PATH export (now every time I Install NodeJS it asks me to do a new export, where I also should remove the previous one.

@abhi007tyagi
Copy link

abhi007tyagi commented Feb 6, 2020

Either ncu or npm-check-updates aren't found after installing!

PS E:\Abhinav_Workspace\NodeProject> ncu
ncu : The term 'ncu' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1

  • ncu
  •   + CategoryInfo          : ObjectNotFound: (ncu:String) [], CommandNotFoundException
      + FullyQualifiedErrorId : CommandNotFoundException
    
    

PS E:\Abhinav_Workspace\NodeProject> npm-check-updates
npm-check-updates : The term 'npm-check-updates' is not recognized as the name of a cmdlet, function, script file, or
operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
again.
At line:1 char:1

  • npm-check-updates
  •   + CategoryInfo          : ObjectNotFound: (npm-check-updates:String) [], CommandNotFoundException
      + FullyQualifiedErrorId : CommandNotFoundException
    

@Flexxkii
Copy link

Either ncu or npm-check-updates aren't found after installing!

PS E:\Abhinav_Workspace\NodeProject> ncu
ncu : The term 'ncu' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1

  • ncu
  •   + CategoryInfo          : ObjectNotFound: (ncu:String) [], CommandNotFoundException
      + FullyQualifiedErrorId : CommandNotFoundException
    

PS E:\Abhinav_Workspace\NodeProject> npm-check-updates
npm-check-updates : The term 'npm-check-updates' is not recognized as the name of a cmdlet, function, script file, or
operable program. Check the spelling of the name, or if a path was included, verify that the path is correct and try
again.
At line:1 char:1

  • npm-check-updates
  •   + CategoryInfo          : ObjectNotFound: (npm-check-updates:String) [], CommandNotFoundException
      + FullyQualifiedErrorId : CommandNotFoundException
    

You need to install npm-check-updates globally
So
npm install -g npm-check-updates

now do
ncu

@pekumar7
Copy link

pekumar7 commented May 4, 2020

Same thing happening for me on windows .. @Flexxkii -installed successfully ( install npm-check-updates globally--> + [email protected]) but ncu not working.. Please advise..

@hermit-Z
Copy link

hello everyone, I have corrected this problem with the following instructions:
sudo npm install -g npm-check-updates

@hosseinGanjyar
Copy link

I had this problem and solved by this solutiob:

Run npm config get prefix and check the correct npm path first and append the output to the PATH using command or adding manually.

npm config get prefix => C:\mydev\tools\npm\npm

set PATH=%PATH%;C:\mydev\tools\npm\npm

@naveen106
Copy link

Can you please elaborate, what is this PATH? Is it environment variable in system settings? I tried running your those 2 lines of yours, first ran, but second didn't.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants