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

Cannot find module 'npmlog' after upgrading to NodeJS 4.0 #2814

Closed
cedon opened this issue Sep 11, 2015 · 14 comments
Closed

Cannot find module 'npmlog' after upgrading to NodeJS 4.0 #2814

cedon opened this issue Sep 11, 2015 · 14 comments
Labels
npm Issues and PRs related to the npm client dependency or the npm registry. question Issues that look for answers. windows Issues and PRs related to the Windows platform.

Comments

@cedon
Copy link

cedon commented Sep 11, 2015

After upgrading to NodeJS 4.0 on Windows 10 x64, npm is completely unusable giving me the following:

module.js:338
throw err;
^

Error: Cannot find module 'npmlog'
at Function.Module._resolveFilename (module.js:336:15)
at Function.Module._load (module.js:286:25)
at Module.require (module.js:365:17)
at require (module.js:384:17)
at C:\Users\Cedon\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js:18:11
at Object. (C:\Users\Cedon\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js:75:3)
at Module._compile (module.js:434:26)
at Object.Module._extensions..js (module.js:452:10)
at Module.load (module.js:355:32)
at Function.Module._load (module.js:310:12)

I have done just about everything I can think of short of downgrading back to 0.12.7. Reinstalls result in the same problem.

@mscdex mscdex added windows Issues and PRs related to the Windows platform. npm Issues and PRs related to the npm client dependency or the npm registry. labels Sep 11, 2015
@mathiask88
Copy link
Contributor

C:\Users\Cedon\AppData\Roaming\npm is the path for global installed modules, so if I have to guess, your global installed npm is not up to date. Try to remove the global installed npm and use the build in version, that comes with the node installer. To remove the global installed npm delete the npm and npm.cmd files in C:\Users\Cedon\AppData\Roaming\npm and the folder npm in C:\Users\Cedon\AppData\Roaming\npm\node_modules.

@cedon
Copy link
Author

cedon commented Sep 11, 2015

That did it. I thought I swept everything out but looks like that got missed. Thanks.

@thstarshine
Copy link

thanks @mathiask88 ! deleting those files fixes node-gyp build issue for me.

@rcheuk
Copy link

rcheuk commented Dec 17, 2015

thanks @mathiask88 this solved my issue too!

@abhineet-mishra
Copy link

thanks a lot @mathiask88. The issue got fixed with your answer.

@myselfsufiyan
Copy link

thanks @mathiask88 solves my issue too... :)

@harvest316
Copy link

thanks @mathiask88 that worked.

@abcdGJJ
Copy link

abcdGJJ commented Apr 29, 2016

thanks @mathiask88 it's ok

@ritox842
Copy link

worked for me..
Thanks @mathiask88

@Efren-Barragan
Copy link

Hello, I am new to node.js but I keep getting this problem on my command prompt. I am also new to the command prompt...thanks!

Microsoft Windows Version 10.0.10586 2015 Microsoft Corporation. All rights reserved.

C:\Users\Efren Barragan>AppData\Roaming\npm
'AppData\Roaming\npm' is not recognized as an internal or external command,
operable program or batch file.

@nicolasgaviola
Copy link

Thanks @mathiask88. Worked for me!

@makazeu
Copy link

makazeu commented Sep 22, 2016

@mathiask88 Thanks! It helps a lot!

@htran81
Copy link

htran81 commented Oct 14, 2016

@mathiask88 Thanks you! It worked for me.

@gameboyzone
Copy link

@mathiask88 - Thanks, it worked!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
npm Issues and PRs related to the npm client dependency or the npm registry. question Issues that look for answers. windows Issues and PRs related to the Windows platform.
Projects
None yet
Development

No branches or pull requests