You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When trying to get caching on travis to work for my front-end packages, I found that bower update doesn't do what I expected it to do, namely to
Check which packages and versions are installed under bower_components and
Update the ones that don't match the specs in bower.json.
Instead, what happens is that all packages are overridden by whatever is specified in bower.json, no matter if they are up-to-date or not. This results in our travis tests taking 30% longer than necessary.
Any comments, opinions, hints here?
The text was updated successfully, but these errors were encountered:
When trying to get caching on travis to work for my front-end packages, I found that
bower update
doesn't do what I expected it to do, namely tobower_components
andbower.json
.Instead, what happens is that all packages are overridden by whatever is specified in
bower.json
, no matter if they are up-to-date or not. This results in our travis tests taking 30% longer than necessary.Any comments, opinions, hints here?
The text was updated successfully, but these errors were encountered: