{"action":"opened","issue":{"url":"https://api.github.com/repos/bower/bower/issues/1791","labels_url":"https://api.github.com/repos/bower/bower/issues/1791/labels{/name}","comments_url":"https://api.github.com/repos/bower/bower/issues/1791/comments","events_url":"https://api.github.com/repos/bower/bower/issues/1791/events","html_url":"https://github.com/bower/bower/issues/1791","id":72357973,"number":1791,"title":"Discussion: The Component Management Mess","user":{"login":"bdkjones","id":926566,"avatar_url":"https://avatars.githubusercontent.com/u/926566?v=3","gravatar_id":"","url":"https://api.github.com/users/bdkjones","html_url":"https://github.com/bdkjones","followers_url":"https://api.github.com/users/bdkjones/followers","following_url":"https://api.github.com/users/bdkjones/following{/other_user}","gists_url":"https://api.github.com/users/bdkjones/gists{/gist_id}","starred_url":"https://api.github.com/users/bdkjones/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/bdkjones/subscriptions","organizations_url":"https://api.github.com/users/bdkjones/orgs","repos_url":"https://api.github.com/users/bdkjones/repos","events_url":"https://api.github.com/users/bdkjones/events{/privacy}","received_events_url":"https://api.github.com/users/bdkjones/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-05-01T05:23:37Z","updated_at":"2015-05-01T05:23:37Z","closed_at":null,"body":"This issue is a discussion of the current state of how Bower manages component information. I'll illustrate the problem using two examples:\r\n\r\n\r\n### JQuery Missing\r\n\r\nIf you go to bower.io/search right now and search for \"jQuery\", the main jQuery component is missing. You'll get a bunch of plugins and things like jQuery UI, JQuery Color, etc, but the main jQuery component is not returned. I confirmed this by pulling the JSON file that the search routine hits. It's nowhere in that list. It was there earlier, it's not now. To prove this, here's a screenshot of the results: \r\n\r\n![screen shot 2015-04-30 at 22 21 06](https://cloud.githubusercontent.com/assets/926566/7427022/4579c442-ef87-11e4-878d-10de81b88def.png)\r\n\r\n\r\n\r\n### Breakpoint-Sass\r\n\r\nIf you use the CLI to pull up info about `breakpoint-sass`, you'll see that it lists this as the URL for homepage: 'https://github.com/Team-Sass/breakpoint' That URL is 404-ed. \r\n\r\nWhen you run `bower install breakpoint-sass`, the CLI is pulling version 2.5.0 of breakpoint-sass using this URI: https://github.com/Team-Sass/breakpoint/archive/v2.5.0.tar.gz\r\n\r\nThat URI is still valid; if you load it in your browser, it will pull down the package. But the rest of that link is dead and breakpoint-sass has moved to a new home at: https://github.com/at-import/breakpoint\r\n\r\nIf you attempt to go to the old GitHub page, it redirects to the new one. But the Bower CLI is still pulling from the old, dead repo. The bower.io/search page, however, loads the NEW URL for breakpoint-sass. (Because the search page is pulling from a different JSON list at herokuapp.com than the CLI pulls from). \r\n\r\n\r\n### How Can We Fix This?\r\n\r\nThe examples above are two of about 3,500 that I've identified. (I write CodeKit and I have a script that hits the same JSON list that the CLI uses and retrieves info about each component.) But the CLI list has TONS of incorrect information, such as the outdated links for breakpoint-sass. Many of the repos are 404-ed. There are components literally named `\"\"` and `\" \"`. (That's a component with no name and a component with a space character for the name.)\r\n\r\nIt's becoming a bit untenable trying to make sense of the way Bower handles components. The CLI is doing one thing, but the public search website is doing another. There's two separate lists of components for each of these and both have big errors and omissions (the search list currently doesn't have jQuery!)\r\n\r\nThere's got to be a better way, right? Can we consolidate Bower's sources so that there is **ONE** canonical list of components that is correct? Can we implement a way for component authors to update their information when they, for example, move a repo?\r\n\r\nIs there a solution being worked on? If so, can we prioritize that? \r\n\r\nIn short: can we get a One Ring To Rule Them All?\r\n\r\n "}}