EINVRES请求https://bower.herokuapp.com/packages/失败,502 [英] EINVRES Request to https://bower.herokuapp.com/packages/ failed with 502
问题描述
Bower安装失败,502-Bad Gateway。
例如,ember库的bower安装在命令行中给出以下响应。
EINVRES要求 https:// bower .herokuapp.com / packages / ember 失败
with 502
当 http://bower.herokuapp.com/ 直接从网址访问,它会提供以下信息。
不推荐使用此Bower版本。请更新它:npm install -g
bower。新的注册地址为 https://registry.bower.io
Bower正在弃用他们使用Heroku托管的注册表。 http://bower.herokuapp.com/ 将无法再访问,或者可能会间歇性地关闭,因此,强迫用户使用新的注册表。
使用旧版本的bower版本的用户可以更新 .bowerrc 文件以下数据。
{
registry:https://registry.bower.io
}
.bowerrc 文件可以是位于 bower.json 和 bower_components 文件夹所在的文件夹中。如果它不存在,你可以制作一个。
如需参考,请查看以下链接
- https://twitter.com/bower/status/918073147789889536
- https://gist.github.com/sheerun/c04d856a7a368bad2896ff0c4958cb00
Bower install fails with 502 - Bad Gateway when downloading bower packages.
For example bower install for ember library gives following response in command line.
EINVRES Request to https://bower.herokuapp.com/packages/ember failed with 502
When http://bower.herokuapp.com/ is accessed directly from URL it gives the following message.
This Bower version is deprecated. Please update it: npm install -g bower. The new registry address is https://registry.bower.io
Bower is deprecating their registry hosted with Heroku. http://bower.herokuapp.com/ Will not be accessible anymore or it might be down intermittently, therefore, forcing users to a new registry.
Users working on old bower versions can update the .bowerrc file with the following data.
{
"registry": "https://registry.bower.io"
}
.bowerrc file can be located at the same folder where bower.json and bower_components folder is located. If it is not present already, you can make one.
For references check the below links
- https://twitter.com/bower/status/918073147789889536
- https://gist.github.com/sheerun/c04d856a7a368bad2896ff0c4958cb00
这篇关于EINVRES请求https://bower.herokuapp.com/packages/失败,502的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!