Bower doesn't update my scripts #971

Closed
justnorris opened this Issue Nov 16, 2013 · 5 comments

Projects

None yet

6 participants

@justnorris

Hey Peeps, I'm loving bower, but I can't figure the update system out.
I had Packery 1.0.6 Installed, ( 1.1.2 is out now ) and when I ran bower update it just scanned the directories and didn't update anything at all.
Then I edited the bower.json file and removed Packery 1.0.6 from dependencies and ran bower install packery, then bower got a little confused, asked me which version I wanted - I selected 1.1.2 and now I have 1.1.2. Why didn't it update to 1.1.2 in the first place ? How can I trust Bower that I have the latest version of everything installed ?

@radum

Same question here ... dunno if I'm missing something or not.

@omasback

Same here. bower update doesnt seem to work for me at all. whether just running bower update, or specifying a single component. neither works. only bower install [componentname] will install the latest version of the component, or manually changing componenent version number and then running bower install.

@hotmeteor

Same as above. Are we missing something?

@slaFFik

"jquery": "~1.11" to have the latest jquery in 1.11 branch (that means 1.11.1, 1.11.2 etc). You won't update to 1.12.

"jquery": "latest" to have the latest release, like 2.1 for now. You will upgrade to 2.2, 2.5, 3.0 etc.

Remember about dependencies.

@sheerun

Everything should work in latest bower version.

Your bower was confused because there were packery installed in bower_components and bower checks this directory for installed versions. This will change in 2.0, so only bower.json will be important, not the contents of bower_components.

Until then you need to uninstall components using bower uninstall --save instead editing bower.json manually. Or remove packery from bower_components manually.

@sheerun sheerun closed this Jun 8, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment