-
-
Save sheerun/c04d856a7a368bad2896ff0c4958cb00 to your computer and use it in GitHub Desktop.
{ | |
"registry": "https://registry.bower.io" | |
} |
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?
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
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
Should have been also in the deprecation notices probably ;-)
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
Did you get it to work after using VSCode and CLI? My .bowerrc looks like this as well.
Hi @AditMulyadi,
We got the same error yesterday, and updating the registry, as suggested in this Gist, fixed the issue.
Cheers!