0

I am beginner in React.js and I am trying to Install react through npm BUT i am stuck on an Error.

The Problem

When i try to install npm install react then node server is stuck on [..................] - rollbackFailedOptional: verb npm-session 9a5b1fb467359b45 .

When i type this :-

    > npm config rm proxy
    > npm config rm https-proxy

nothing happens in Terminal

What have i tried ?

1). I have also tried This. BUT this didn't work for me.

EDIT

After some time it is showing fetchMetadata: sill resolveWithNewModule react@17.0.1 checking installable status

Any help would be appreciated.

Thank You in Advance.

Lars
  • 1,234
  • 1
  • 8
  • 31
  • Please provide the full verbatim error message. Are you behind a firewall or proxy? – Thomas Sablik Jan 31 '21 at 11:05
  • Now it is showing `fetchMetadata: sill resolveWithNewModule react@17.0.1 checking installable status `. AND there is no other message – Lars Jan 31 '21 at 11:07
  • @Progam So you did the third (important) line `npm config set registry https://registry.npmjs.org/`, too, right? Could you please `ping registry.npmjs.org` and tell us the outcome? – SimplyComple0x78 Feb 06 '21 at 17:21
  • @Progam if you are using windows you might try your npm commands in administrator terminal, have you tried clearing your npm cache ? – shubham jha Feb 10 '21 at 06:06
  • @shubhamjha, When i reinstall the node and tried again THEN it worked. I think the problem was in running program. – Lars Feb 10 '21 at 11:31
  • @SimplyComple0x78, When i reinstall the node and tried again THEN it worked. I think the problem was in running program. – Lars Feb 10 '21 at 11:31
  • Well, sad to hear, that your node has been broken in some unknown way. Reinstalling is always a last resort - but glad it helped. :) – SimplyComple0x78 Feb 11 '21 at 06:29

2 Answers2

0

Based on the comments (for future visitors), you should try to run npm config set registry https://registry.npmjs.org/. If that doesn't work, try to ping registry.npmjs.org. If the ping works, you should try to reinstall Node.

0xLogN
  • 3,289
  • 1
  • 14
  • 35
  • When i reinstall the node and tried again THEN it worked. I think the problem was in running program – Lars Feb 12 '21 at 09:51
0

When i reinstall the node and tried again THEN it worked.

Lars
  • 1,234
  • 1
  • 8
  • 31