Proper .bowerrc file pointing to new Bower registry (if using legacy Bower version)

.bowerrc

{
  "registry": "https://registry.bower.io"
}

Why deprecate old registry url? The current domain of registry hardcored into Bower (https://bower.herokuapp.com) belongs to Heroku. It means we have no control over it and that presents at least two serious disadvantages:

1. We're dependent on Heroku for hosting of the registry (currently they kindly provide us with credits but we can't expect it forever)
2. We are unable to change DNS of this domain to, for example, put it behind CDN for reduced costs and latency.

To fix this, we released patches for each Bower version that change registry url to https://registry.bower.io It's enough to upgrade.

In case someone is unable to upgrade Bower (not recommended), the .bowerrc file presented above needs to be added to a project.

Why deprecate old registry url? The current domain of registry hardcored into Bower (https://bower.herokuapp.com) belongs to Heroku. It means we have no control over it and that presents at least two serious disadvantages:

1. We're dependent on Heroku for hosting of the registry (currently they kindly provide us with credits but we can't expect it forever)
2. We are unable to change DNS of this domain to, for example, put it behind CDN for reduced costs and latency.

To fix this, we released patches for each Bower version that change registry url to https://registry.bower.io It's enough to upgrade.

In case someone is unable to upgrade Bower (not recommended), the .bowerrc file presented above needs to be added to a project.

You really should set up a redirect from the old to the new host, this is a really hard breaking change.

You really should set up a redirect from the old to the new host, this is a really hard breaking change.

:') welcome to the javascript world

:') welcome to the javascript world

A redirect and notice wouldn't have gone amiss. Our builds are now failing because we were unaware of this change.

A redirect and notice wouldn't have gone amiss. Our builds are now failing because we were unaware of this change.

Its a good thing there was a lot of warning and deprecation notices in the console leading up to this. :P

Its a good thing there was a lot of warning and deprecation notices in the console leading up to this. :P

We also have this problem
bower jquery#2.1.4 EINVRES Request to https://bower.herokuapp.com/packages/jquery failed with 410

We also have this problem
bower jquery#2.1.4 EINVRES Request to https://bower.herokuapp.com/packages/jquery failed with 410

Thank god, you said this. My builds eventually fail and I have no idea why they did. But Thanks though

Thank god, you said this. My builds eventually fail and I have no idea why they did. But Thanks though

This is really hard figure it out what happen in build failing. Please try to put additional warning or notices.

This is really hard figure it out what happen in build failing. Please try to put additional warning or notices.

In my CI environment I'm installing Bower 1.8.2, the latest version according to the GH repo, and I am still getting 410 errors. The only thing that fixed this for me was manually setting the registry in .bowerrc.

In my CI environment I'm installing Bower 1.8.2, the latest version according to the GH repo, and I am still getting 410 errors. The only thing that fixed this for me was manually setting the registry in .bowerrc.

😒

😒

I was still getting the 410 errors and here's the road to my solution. TL;DR: I think it was nvm's fault, reenable your node version.

• I upgraded bower using npm upgrade -g bower
• Then I verified the version was 1.8.2 with bower -v
• When I ran bower install it still gave me 410 errors.
• When I ran it with verbose output bower install -V the end of the output showed as it was still using version 1.7.9.
• Running which bower would show the path to the correct version.
• It seems like nvm might be doing something wonky behind the scenes.
• The way I solved it:
  • Re-source bash settings: source ~/.bash_profile
  • Remind nvm which version of node to use: nvm use 5.12.0 (I know I'm a bit behind)
  • Clear cache: bower cache clean
  • Try again: bower install
  • Success, have a beer.

Your milage may vary.

I was still getting the 410 errors and here's the road to my solution. TL;DR: I think it was nvm's fault, reenable your node version.

• I upgraded bower using npm upgrade -g bower
• Then I verified the version was 1.8.2 with bower -v
• When I ran bower install it still gave me 410 errors.
• When I ran it with verbose output bower install -V the end of the output showed as it was still using version 1.7.9.
• Running which bower would show the path to the correct version.
• It seems like nvm might be doing something wonky behind the scenes.
• The way I solved it:
  • Re-source bash settings: source ~/.bash_profile
  • Remind nvm which version of node to use: nvm use 5.12.0 (I know I'm a bit behind)
  • Clear cache: bower cache clean
  • Try again: bower install
  • Success, have a beer.

Your milage may vary.

Hello,
I found this error message when i run bower install on circleci

bower EINVRES       Request to https://bower.herokuapp.com/packages/jquery failed with 502
bower install returned exit code 1

anyone knows the problem why? Is how to fix it the same as above problem ?
Thanks

Hello,
I found this error message when i run bower install on circleci

bower EINVRES       Request to https://bower.herokuapp.com/packages/jquery failed with 502
bower install returned exit code 1

anyone knows the problem why? Is how to fix it the same as above problem ?
Thanks

Hi @AditMulyadi,
We got the same error yesterday, and updating the registry, as suggested in this Gist, fixed the issue.
Cheers!

Hi @AditMulyadi,
We got the same error yesterday, and updating the registry, as suggested in this Gist, fixed the issue.
Cheers!

My builds were also failing because of bower.herokuapp.com being down since yesterday. I confirm that setting the registry as suggested in this gist fixes the problem. Thanks :) 👍

My builds were also failing because of bower.herokuapp.com being down since yesterday. I confirm that setting the registry as suggested in this gist fixes the problem. Thanks :) 👍

How to update registry if I'm not using bower at all (I have no .bowerrc) but it needs for framework?

How to update registry if I'm not using bower at all (I have no .bowerrc) but it needs for framework?

The other option here is to just move your dependencies to npm or yarn

The other option here is to just move your dependencies to npm or yarn

You can use bower-away to switch to yarn and preserve the rest of your setup

You can use bower-away to switch to yarn and preserve the rest of your setup

my .bowerrc looks like this
{
"directory": "wwwroot/lib",
"registry": "https://registry.bower.io"
}
still can't install or update anything "Using Visual Studio 2018 in a dotnet core 2.0 web application project "

Gonna give a try with VSCode and CLI

my .bowerrc looks like this
{
"directory": "wwwroot/lib",
"registry": "https://registry.bower.io"
}
still can't install or update anything "Using Visual Studio 2018 in a dotnet core 2.0 web application project "

Gonna give a try with VSCode and CLI

The newest version of bower really should point to the new registry by default, not the old one. Without this thread I would have been lost. Thanks @sheerun

The newest version of bower really should point to the new registry by default, not the old one. Without this thread I would have been lost. Thanks @sheerun