npm install Error: rollbackFailedOptional

node.jsReact NativeNpm

node.js Problem Overview

When I try npm install new packages it shows me this error:

> rollbackFailedOptional: verb npm-session 585aaecfe5f9a82

node --version
8.4.0

npm --version
5.3.0

node.js Solutions

Solution 1 - node.js

    # first this
    > npm config rm proxy
    > npm config rm https-proxy

    # then this
    > npm config set registry https://registry.npmjs.org/

solved my problem.

Again: Be sure to check whether you have internet connected properly.

Solution 2 - node.js

Try this

npm config rm proxy
npm config rm https-proxy

Solution 3 - node.js

In my case I had to edit the .npmrc directly and add the proxy settings manually.

proxy=http://yourorganizationproxy.com:8080
https-proxy=http://yourorganizationproxy.com:8080

Hope this helps someone.

Solution 4 - node.js

The cause for this might be your current NPM registry. Try to check for a .npmrc file. These can be at various locations:

  • per-project config file (/path/to/my/project/.npmrc)
  • per-user config file (~/.npmrc)
  • global config file ($PREFIX/etc/npmrc)
  • npm builtin config file (/path/to/npm/npmrc)

Within these there can be something like

registry=https://mycustomregistry.example.org

which will take priority over the default one (http://registry.npmjs.org/). You can delete this line in the file or use the default registry like that:

npm <command> --registry http://registry.npmjs.org/

Solution 5 - node.js

Most likely to be npm registry cannot be reached by npm. Check npm proxy configuration

I had exactly the same issue on Windows Server 2008 R2. I suspected Internet Explorer's Enhanced Security Configuration at first but after turning that off with no success the issue turned out to be that npm was not configured to use my corporate proxy connection to the internet.

It turns out that npm does not use the proxy settings in effect via Internet Options > Connections tab > LAN settings where the server is set to 'Automatically detect settings'. Being set to automatically detect settings does not guarantee that a proxy is indeed being used, it just means that Windows will automatically configure proxy settings for Internet Explorer if it finds a special'wpad.dat' file at http://wpad.[yourdomain.com]/wpad.dat.

You can test whether a wpad.dat file is in use in your organisation by typing the following into a web browser.

http://wpad.[yourcompany.domain]/wpad.dat

If no file is available then it is likely you are not using an organization-wide proxy. If one does get returned to the browser then...

Toward the bottom of this file, you should see a line saying

PROXY <host:port>;

It might be repeated if you have multiple proxies available. The host and port are needed in order to tell npm to use the proxy settings like so:

npm config set proxy http://[host]:[port]

and

npm config set https-proxy http://[host]:[port]

For example if your proxy is at my.proxy.com on port 8080 then the npm commands would be:

npm config set proxy http://my.proxy.com:8080
npm config set https-proxy http://my.proxy.com:8080

Once I had told npm which proxy to use all started working in I was able to run the install commands without a problem.

Thanks to the following post for help with the wpad file discovery.

Solution 6 - node.js

In my case I had my npm set registry set to https://nexus, use:

npm config delete registry

This will revert to its default state.

Solution 7 - node.js

I tried following options to fix this issue and it worked.

  1. Uninstall Node.js version 8.
  2. Install Node.js version 6.11.4
  3. Use the registry option along with command to install any package.

For example to install express I used following command.

npm install express --registry http://registry.npmjs.org/

or

npm install express -g --registry http://registry.npmjs.org/

If you want to install locally in any specific folder then use below command. Below command will install express on path C:\Sample\Example1 .

C:\Sample1\Example1> npm install /Sample/Example1 express --registry http://registry.npmjs.org/

Note: If you are installing locally in a specific location then first go to that directory using command and then run above command. If you are not inside that directory and giving only path in command that will not work.

If you get package.json missing error then run below command before installing package locally

C:\Sample\Example1> npm init

above command will create package.json file. No need to provide any data. just hit enter.

Note: If you are behind a firewall then you may need to set a proxy.

Solution 8 - node.js

Hi I'm also new to react and I also faced this problem after so many trouble I found solution: Just run in your command prompt or terminal :

npm config set registry http://registry.npmjs.org/

This will resolve your problem. Reference link: http://blog.csdn.net/zhalcie2011/article/details/78726679

Solution 9 - node.js

Make sure you can access the corporate repository you configured in npm is available.Check you VPN connection.

Else reset it back to default repository like below.

npm config set registry http://registry.npmjs.org/

Good Luck!!

Solution 10 - node.js

The following commands resolved my issue:

npm config set proxy http://yourproxyurl.com:8080  (you need to enter your or your company proxy URL and 8080 should be replaced by your proxy port)
    
npm config set https-proxy http://yourproxyurl.com:8080

Solution 11 - node.js

I had the same effect creating a react app with PhpStorm. And then at the end it just says done. Running the same command in the terminal gave me detailed errors. The project folder I've created was named react which seems to be a no-go.

Make sure your project folder is not named react.

Solution 12 - node.js

If you have access to the registry but the error is still occurred nothing mentioned above wouldn't work. I noted that this problem is only applicable for local project's installation (i.e. if you use -g to global install everything is working fine).

What's resolved the problem for me: just remove an entry regarding a package you're going to install from a project's package.json file. After that next call to npm will work and install the package successfully.

Solution 13 - node.js

Seem this bug is not fixed yet [1]. Some people get worked, some people not. I also get not worked.

I tried clear cache with command: npm cache verify then run install command again. I got worked.

[1]. https://github.com/npm/npm/issues/17246

Solution 14 - node.js

I had the same issue. But it can run properly with switching from company's internal network to visitor network.

Solution 15 - node.js

I set two system environment variables -

  1. HTTP_PROXY = <proxy_url>
  2. HTTPS_PROXY = <proxy_url>

This actually worked for me.

Solution 16 - node.js

In some rarer occasions, check that the project can be built using regular npm commands. I ran into one that is configured to work with bower, so bower install <github_url> works while npm install <github_url> gives that unhelpful cryptic error message on all platforms...

Solution 17 - node.js

While installing the Angular Command line tool (CLI), If you are getting Rollback Error then it may be occurring due to your network is connected with your Client Network or your Company Network where you are working on.

So Please try to install CLI in your public network (or Your Mobile's hotspot Network) then you would definitely get CLI installed.

Solution 18 - node.js

Solution: The default value of ‘proxy’ and ‘https-proxy’ key of npm config is NULL. After doing some more R & D then I tried to set the proxy setting value to above key (this solution works in my scenario).

Also, the same proxy settings need to be applied in IE browser Internet Settings >> Settings >> LAN settings.

Conclusion: In corporate/some environment the proxy is a somewhat mandatory setting otherwise npm install will not work.

Issue on GitHub: https://github.com/SharePoint/sp-dev-docs/issues/3266

You can refer blog for detailed information https://blogs2share.blogspot.com/2019/01/spfx-environment-setup-error.html

Solution 19 - node.js

You can resolve the issue by looking if your network has any proxies, that is prohibiting the download process. My company's network had a firewall enabled, which was causing the issue for me. So I had to switch to an un-secure network (probably a hotspot from your mobile network), and that worked for me.

Solution 20 - node.js

Mine was due to McAfee firewall. It is set to Ask mode, so should have popped up a prompt to ask for internet connection, but it didn't! Going into McAfee and (temporarily!) disabling the firewall allowed me to install.

Solution 21 - node.js

I've already had the proxies set as described above and it was working until today. Then it turned out that now I need "http://" in front of my proxy address: "http://{proxyURL}:{proxyPort}". Then it finally worked.

Solution 22 - node.js

Struggled with this issue for some time before figuring it out.
I'm using High Sierra (10.13.6)
Uninstalled and re-installed node and nvm multiple times - using the installer.pkg, HomeBrew, and then using the command line. IMO, the command line works the best.

I followed these steps:

  1. Ran npm config ls -l

  2. Checked that the value for globalconfig was $<installpath>/.nvm/versions/node/v12.16.3/etc/npmrc But when I tried to get to this path in the Terminal, it gave me No such file or directory
    So I

  3. created the folder etc, created the npmrc file and added this line in it.

    registry = "https://registry.npmjs.org/"
    I do not have the ~/.npmrc file in my $HOME

    Then

  4. I re-ran the npm install command.


Note that this still threw the rollbackFailedOptional: verb npm-session error, but this time it completed, though with a different error. You could try these steps and see if it works.

For those who are curious, it threw a Response timeout while trying to fetch https://registry.npmjs.org/<package> (over 30000ms) error, so I added the timeout = "60000" to the /etc/npmrc file (as found on another Stackoverflow thread), and tried again. This worked for me.

Hope this helps!

Solution 23 - node.js

Try this all command answered here to solve the problem https://stackoverflow.com/a/54173142/12142401 if problem persists Do the following Steps

> Completely Uninstall the nodejs checkout this answer for complete uninstallation of nodejs https://stackoverflow.com/a/20711410/12142401 > > Download the updated nodejs setup from their website > Install it in any drive but not on previously installed drive like if you installed in C drive then install in D,S,G Drive > Run your npm command it will completely work fine

Solution 24 - node.js

If you use vpm as I do, try turn it off a sec, at least that's my problem

Solution 25 - node.js

I had same problem. I deleted files in my Mac "/usr/local/bin/npm", "/usr/local/bin/node" and deleted folder "/usr/local/lib/node_modules"

and then installed the current latest feature version of node. then problem solved.

When downloaded LTS version, it shows the same problem. So, try installing different versions of node and deleting old one.

Solution 26 - node.js

try this:

delete all file in folder: %APPDATA%\npm-cache\_locks

Solution 27 - node.js

For Windows: Run the installer again and choose to 'Repair' the installation

Worked for me

Solution 28 - node.js

Try this. It worked fine for me

> npm install /your_floder_location package_name --registry > http://registry.npmjs.org/

Below is the exact command for me for installing vue-router package in my laravel project (my project name vue_laravel)

> aslam004:vue_laravel $ npm install > /var/www/html/projects/vue_laravel vue-router --registry http://registry.npmjs.org/

Good luck

Solution 29 - node.js

use sudo before your command as

sudo npm install

Categories
Recommended node.js Solutions
Recommended React Native Solutions
Recommended Npm Solutions

Previous Solution:

Only on Firefox "Loading failed for the <script> with source"

JavascriptPhpJqueryFirefoxYii

Next Solution:

Lambda implicit capture fails with variable declared from structured binding

C++LambdaVisual Studio-2017C++17Structured Bindings

Attributions

All content for this solution is sourced from the original question on Stackoverflow.

The content on this page is licensed under the Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.

Content TypeOriginal AuthorOriginal Content on Stackoverflow
QuestionBipul PrasaiView Question on Stackoverflow
Solution 1 - node.jsanvarikView Answer on Stackoverflow
Solution 2 - node.jscwtuanView Answer on Stackoverflow
Solution 3 - node.jsmiqrcView Answer on Stackoverflow
Solution 4 - node.jslambdaView Answer on Stackoverflow
Solution 5 - node.jsAnotherLongUsernameView Answer on Stackoverflow
Solution 6 - node.jsLuis AceroView Answer on Stackoverflow
Solution 7 - node.jsAnilView Answer on Stackoverflow
Solution 8 - node.jsRails DeveloperView Answer on Stackoverflow
Solution 9 - node.jsRudraView Answer on Stackoverflow
Solution 10 - node.jsBrooklyn99View Answer on Stackoverflow
Solution 11 - node.jsMarkus ZellerView Answer on Stackoverflow
Solution 12 - node.jsAlex EvseenkoView Answer on Stackoverflow
Solution 13 - node.jsNgaNguyenDuyView Answer on Stackoverflow
Solution 14 - node.jsClimberView Answer on Stackoverflow
Solution 15 - node.jsH S RajuView Answer on Stackoverflow
Solution 16 - node.jsprusswanView Answer on Stackoverflow
Solution 17 - node.jsAmit KumarView Answer on Stackoverflow
Solution 18 - node.jsVikas BansalView Answer on Stackoverflow
Solution 19 - node.jsNikhil KumarView Answer on Stackoverflow
Solution 20 - node.jsantonyeView Answer on Stackoverflow
Solution 21 - node.jsLiebster KameradView Answer on Stackoverflow
Solution 22 - node.jsSoumitraView Answer on Stackoverflow
Solution 23 - node.jsuser12142401View Answer on Stackoverflow
Solution 24 - node.jsEnfield liView Answer on Stackoverflow
Solution 25 - node.jsRaman KumarView Answer on Stackoverflow
Solution 26 - node.jsFurettoView Answer on Stackoverflow
Solution 27 - node.jslokeshrmitraView Answer on Stackoverflow
Solution 28 - node.jsAslam AnsariView Answer on Stackoverflow
Solution 29 - node.jsAnkit GaurView Answer on Stackoverflow