angular cli - install stuck when extract rxjs

[Nagarajan8194]

when run "npm install -g @angular/cli" it will run for some time and its get struck when extracting rxjs . Please help me. i already set proxy configuration.

Versions

node version :
8.10.0
NPM version :
5.6.0
am using windows 10.

Repro steps

when installation get stuck:
extract:rxjs: sill pacote rxjs@https://registry.npmjs.org/rxjs/-/rxjs-5.5.6.tgz extracted to C:\Users\p00115856\AppData\Roaming\npm\node_modules

• Step 1
• Step 2
• Step 3

Observed behavior

<!-- Normally this includes a stack trace and some more information. -->

Desired behavior

Mention any other details that might be useful (optional)

[ZackKnopp]

Possible duplicate of #8367

I followed @avalanchy's solution and it worked for me.

"Ok, it unfreezes after a long time.

From the output grabbed this gyp WARN EACCES user "root" does not have permission to access the dev dir "/root/.node-gyp/8.9.1". After googling this line I found a solution of adding an extra flag "unsafe-perm" (which is not documented in npm install manual) that fixes the problem:

sudo npm i --unsafe-perm --verbose -g @angular/cli "

[Brocco]

This appears to be an npm installation issue, which is not something that we're able to assist with, please see the possible duplicate issue above.

[gfaganli]

i also have the same problem while upgrading to angular 6, any solution?

[jmaFinistereVar]

I have the exact same problem using windows10, node v8.9.3, npm5.5.1
I tried
npm install --unsafe-perm
but the command freezes

extract:rxjs: sill pacote rxjs@https://registry.npmjs.org/rxjs/-/rxjs-6.2.2.tgz

[geekyarthurs]

use administrator permission to open cmd :) 💯

[ashraphs]

hi guys, any fix ?
already open the cmd as admin, but still stuck

[radhemohan]

By providing write access to node_modules and installing packages by
npm i --unsafe-perm --verbose install
Solved my problem. Thanks to all

[opit]

@ashraphs its a long shot, but are you running in a vagrant VM? npm install creates a lot of I/O on the virtual machine that might make it crash. I just ran into this issue this morning on ubuntu/bionic64 see error description here: https://www.virtualbox.org/ticket/16417

Only occurs on a shared folder though, so hotfix for me was to copy the package.json in a folder that was not shared between guest and host system, run npm -i there and then cp -r the node_modules folder over afterwards.

Good luck.

[presidiomep]

I had the SAME issue: installation stalled on rsjx. Closed down the terminal, and restarted the process again, same issue the second time, BUT, I decided to let it sit and came back 30 mins later and it worked! I guess it just took time??

[Peter1234444]

@radhemohan found your solution worked thanks!
Instead of "npm i --unsafe-perm --verbose install" I wrote
sudo npm i --unsafe-perm --verbose install

not sure if adding sudo actually did anything or not but the code still worked fine.

[smartnav]

Install dependency one by one then it will work.

[Radhakrishna-ab]

If you are running behind proxy, Configure proxy for npm and Git by running below commands.
NPM:
$ npm config set https-proxy http://proxy.[Company Name].com:8080
$ npm config set https-proxy http://proxy.[Company Name].com:8080

In case proxy needs credentials, you need to pass credentials like below,
$ npm config set https-proxy http://:@Proxy.[Company Name].com:[Port]
$ npm config set https-proxy http://:@Proxy.[Company Name].com:[Port]

Git:
$ git config --global http.proxy http://:@:

This Resolved my problem. Hope this info will help you all

[hypnotic-frog]

This is why I hate Node and all the related sh.... that comes with it. The process of problem solving is so arbitrary you never know what to expect.
I sincerely hope some day when I hit npm install, the floor cracks and I finally may die burned by the flames of hell, so I have not to suffer all of this over again.

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}