-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Force Bower reinstall #37
Comments
I have the same issue. Running "mimosa bower:clean", it removes all bower installed assets. So you'd think that running "mimosa bower" thereafter would cause a full re-install of all bower deps. But it just says no bower installs are necessary, even though it just deleted them all from my assets folder. Only way to get reinstall is to do a rm -rf .mimosa/bower, the run "mimosa bower". For me, at least. |
Yes, and while it could be something like a |
@zaceno I can't reproduce that. With latest mimosa
The last It works this way if I use |
I can get behind a I'm a little leery about introducing a top level flag for something specific to a module like this. Maybe a Can't use |
Added the |
@dbashford : I was running an older Mimosa. With 2.2.5, I can't reproduce it either. So I withdraw my complaint :) Even so: thumbs up on the --cleanall flag. I frequently find myself deleting the .mimosa folder when debugging things. |
Thanks. I'll give this a shot. |
Maybe this is already possible somehow, but there should be a way to tell mimosa to force a bower reinstall even when it doesn't think there should be one. The only thing I seem to be able to do now is delete `.mimosa/bower', which is a bit of a pain. A command line arg would be ideal.
I'm not sure why this happens to me but sometimes, moving around git branches, I'll lose a vendor file (I don't check them in if they come from Bower) and mimosa still thinks things are cool because I haven't touched anything that normally triggers it. Those are times when a simple force reinstall would be good to have.
The text was updated successfully, but these errors were encountered: