Skip to content
This repository has been archived by the owner on Aug 11, 2022. It is now read-only.

NPM not getting installed correctlly #15410

Closed
3 tasks
RamitAnandSharma opened this issue Jan 6, 2017 · 3 comments
Closed
3 tasks

NPM not getting installed correctlly #15410

RamitAnandSharma opened this issue Jan 6, 2017 · 3 comments

Comments

@RamitAnandSharma
Copy link

I'm opening this issue because:

  • npm is crashing.
  • [/ ] npm is producing an incorrect install.
  • npm is doing something I don't understand.
  • Other (see below for feature requests):

What's going wrong?

Installed Node.js and NPM from node installer v7.4.0
Installed successfully but no npm commands working

How can the CLI team reproduce the problem?

Install node js from
https://nodejs.org/en/

run command
npm -v
npm install -g angular-cli [Gives Errror]
npm [Gives Error]

Error

C:\windows\system32>npm -help
Error: Cannot find module 'bl'
at Function.Module._resolveFilename (module.js:470:15)
at Function.Module._load (module.js:418:25)
at Module.require (module.js:498:17)
at require (internal/module.js:20:19)
at Object. (C:\Users\sbbras\AppData\Roaming\npm\node_modules
\npm\node_modules\request\request.js:9:10)
at Module._compile (module.js:571:32)
at Object.Module._extensions..js (module.js:580:10)
at Module.load (module.js:488:32)
at tryModuleLoad (module.js:447:12)
at Function.Module._load (module.js:439:3)
npm ERR! Windows_NT 6.3.9600
npm ERR! argv "C:\Program Files\nodejs\node.exe" "C:\Users\sbbras\App
Data\Roaming\npm\node_modules\npm\bin\npm-cli.js" "-help"
npm ERR! node v7.4.0
npm ERR! npm v4.0.2
npm ERR! code MODULE_NOT_FOUND

npm ERR! Cannot find module 'bl'

@Ilon4ik
Copy link

Ilon4ik commented Feb 16, 2017

Any Update on this issue?

@legodude17
Copy link
Contributor

Try reinstalling npm.

@npm-robot
Copy link

We're closing this issue as it has gone seven days without activity and without being labeled. If we haven't even labeled in issue in seven days then we're unlikely to ever read it.

If you are still experiencing the issue that led to you opening this or this is a feature request you're still interested in then we encourage you to open a new issue. If this was a support issue, you may be better served by joining package.communty and asking your question there.

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

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

No branches or pull requests

4 participants