Skip to content
This repository has been archived by the owner on Apr 11, 2020. It is now read-only.

Latest React packages not listed in Bower UI #328

Closed
scottaddie opened this issue Dec 7, 2015 · 9 comments
Closed

Latest React packages not listed in Bower UI #328

scottaddie opened this issue Dec 7, 2015 · 9 comments
Assignees

Comments

@scottaddie
Copy link
Member

scottaddie commented Dec 7, 2015

In the new Bower UI, the latest version of the "react" package that's listed in the right panel's drop-down is 0.13.3. When navigating to the project's GitHub repo, I see several other releases, such as 0.14.3, that I would expect to appear in the UI's drop-down.

@sayedihashimi
Copy link
Contributor

Assigning to @madskristensen

@xt0rted
Copy link

xt0rted commented Mar 22, 2016

A similar issue was just reported for angular-ui/bootstrap-bower#68

@sayedihashimi
Copy link
Contributor

TFS Bug#231245

@craigbroadman
Copy link

This is also happening for me using angular-bootstrap and angular/angular-core/angular-mocks etc etc

@craigbroadman
Copy link

Is there any update on this? I thought it might have been resolved in the latest Visual Studio update?

@jansokoly
Copy link

Still an issue after latest VS update. I appreciate the existence of Visual Studio UI for Bower very much, but this issue makes it so much less useful.

@SemperFu
Copy link

SemperFu commented Nov 4, 2016

I'm seeing this issue as well. Thought I was doing something wrong. Font-Awesome is 4.7.0 but the manage bower packages shows 4.6.1 as latest.

@TotzkePaul
Copy link

Same @Jasin2069. In uninstallled and reinstalled all VS and components and clearing cache and temp files. I ran Total Uninstaller. Manually editing the bower.json works well though but I can't update the packages from the UI. All the versions seem to be from June 2016 or earlier.

Even the demo shows 4.6.1 but updating to 4.6.3 for Font Awesome
https://docs.microsoft.com/en-us/aspnet/core/client-side/bower

@jodavis
Copy link

jodavis commented Feb 10, 2017

The Manage Bower Packages UI in VS 2015 was working from a built-in list of packages. In VS 2017, we have switched to using an online search service (libraries.io) so we should not run into out-of-date package versions.

@jodavis jodavis closed this as completed Feb 10, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

9 participants