This comment has been minimized.
This comment has been minimized.
You really should set up a redirect from the old to the new host, this is a really hard breaking change. |
This comment has been minimized.
This comment has been minimized.
:') welcome to the javascript world |
This comment has been minimized.
This comment has been minimized.
A redirect and notice wouldn't have gone amiss. Our builds are now failing because we were unaware of this change. |
This comment has been minimized.
This comment has been minimized.
Its a good thing there was a lot of warning and deprecation notices in the console leading up to this. :P |
This comment has been minimized.
This comment has been minimized.
We also have this problem |
This comment has been minimized.
This comment has been minimized.
Thank god, you said this. My builds eventually fail and I have no idea why they did. But Thanks though |
This comment has been minimized.
This comment has been minimized.
This is really hard figure it out what happen in build failing. Please try to put additional warning or notices. |
This comment has been minimized.
This comment has been minimized.
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. |
This comment has been minimized.
This comment has been minimized.
|
This comment has been minimized.
This comment has been minimized.
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.
Your milage may vary. |
This comment has been minimized.
This comment has been minimized.
Hello,
anyone knows the problem why? Is how to fix it the same as above problem ? |
This comment has been minimized.
This comment has been minimized.
Hi @AditMulyadi, |
This comment has been minimized.
This comment has been minimized.
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 :) |
This comment has been minimized.
This comment has been minimized.
How to update registry if I'm not using bower at all (I have no .bowerrc) but it needs for framework? |
This comment has been minimized.
This comment has been minimized.
The other option here is to just move your dependencies to npm or yarn |
This comment has been minimized.
This comment has been minimized.
You can use bower-away to switch to yarn and preserve the rest of your setup |
This comment has been minimized.
This comment has been minimized.
my .bowerrc looks like this Gonna give a try with VSCode and CLI |
This comment has been minimized.
This comment has been minimized.
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 |
This comment has been minimized.
This comment has been minimized.
Should have been also in the deprecation notices probably ;-) |
This comment has been minimized.
This comment has been minimized.
Did you get it to work after using VSCode and CLI? My .bowerrc looks like this as well. |
This comment has been minimized.
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:
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.