Reputation: 9575
I need to force bower to override a locally-defined dependency with a fresh copy. I assumed that bower update <package>
would do the trick (even with a little extra --force
). However, it stubbornly prefers whatever copy is installed under bower_components.
Consider the following layout (all in one codebase for now, sadly):
shared/bower.json
{
"name": "mysharedstuff",
"version": "0.0.1",
...
}
client1/bower.json
{
...
"dependencies": {
"mysharedstuff": "../shared"
}
}
The only way I can get a fresh copy of shared/ is to explicitly delete the copy installed under bower_components. For example:
client1$> rm -rf bower_components/mysharedstuff
client1$> bower install
Is this a bug with how bower handles versioning of local dependencies? Or am I missing something simple?
Upvotes: 26
Views: 23790
Reputation: 11
Because bower looking for latest TAG name in your repo. Specify your last commit with git tag.
Upvotes: 1
Reputation: 624
Just to update from the github issue you referenced.
bower --force update
will force update any packages in your bower.json. Works in Bower > v1.3.6
Upvotes: 41