If you search for mjolnic on Bower, you'll see there's a mjolnic-bootstrap-colorpicker repo. The repo has a bower.json pointing to v2.0.0-rc, but when you bower install mjolnic-bootstrap-colorpicker, you get a much older version.
How can I make it so bower defaults to installing the latest version?
"dependencies": {
"mjolnic-bootstrap-colorpicker": "latest"
}
into your bower json
more information here : How to install latest (untagged) state of a repo using bower?
Related
We have an internal library that can be installed via bower install git link. How do I add the git link inside the bower.json file so that when I run bower install, it will install it too?
Didn't know it was easy. I just reinstalled it with --save and it updated my bower.json file. Now I know how it looks like inside the bower.json file.
I'm installing plugins using bower, but bower only downloads Footable v2.0.1, not the latest release of v2.0.1.5.
I've tried:
bower install --save-dev footable
bower install --save-dev footable#2.0.1.x
Both these download v2.0.1, I want the latest tagged release of v2 (v2.0.1.5).
Using #2.0.1.x also gave the error "ENORESTARGET: Tag/Branch 2.0.1.x does not exist".
Bower package versions should follow semantic versioning.
In short, a valid semantic version is in the form of MAJOR.MINOR.PATCH.
2.0.1.5, for example, is not a valid semantic version.
You can get a list of available versions for a package by running the following command:
bower info footable
For footable you the results are:
Available versions:
- 2.0.1
- 2.0.0
- 0.5.0
- 0.1.0
> bower list
momentjs#2.2.1 (2.5.1 now available)
I go to change my bower.json to
{
"version": "0.0.0",
"dependencies": {
"momentjs": "~2.5.1",
...
And then run
> bower cache clean
> bower update momentjs
bower installing momentjs#2.2.1
Why am I getting 2.2.1 and not 2.5.1? Have I misunderstood some basics here?
The help page states that the update command:
Updates installed packages to their newest version according to bower.json
~ will only lookup patch versions in the current minor version range ("prereleases") e.g. 1.2.3 => 1.2.7.
To update the minor version, e.g. 1.2.3 = > 1.3.5, use bower install <package> instead.
I have package bootstrap-calendar
In bower.json it is version 0.2.0-RC and I even updated it to 0.2.0. But no matter what when you run
$> bower install bootstrap-calendar
it attempts to install version 0.0.9 which is earliest version. I cleaned cache but no success. What can I do that on bower install command latest package would be installed?
I don't think this is anything you are doing incorrectly. The package installs for me as 0.0.9 and the js file is listed as 0.1. I think the package is just not correct and needs to be mentioned on the issues section of Github, which I did.
I wanted to install the backbone.routefilter plugin via Bower. It looks like there are 2 projects with that same name. http://sindresorhus.com/bower-components/#!/search/routefilter.
When I try to bower install backbone.routefilter#0.2.0 it tries to install 0.2.0 version from wanderer I want the latest from boazsender. Is there anyway to tell bower which repo to use?
That one seems to be wrongly registered. Use the correct one instead:
bower install backbone.routefilter