0

Situation I have is described here: How to resolve Bower dependency version conflicts?

The problem is that proposed solution does not work. Adding a resolution section to bower.json does nothing and it still requires to choose package version manually on each installation.

But, surprisingly, when I install bower packages though Grunt (with grunt-bower-task), it just works, even without resolutions.

I have the latest bower version (1.4.1 for now).

Does anybody know what's going on and is it possible to make bower to install without manual resolution?

Community
  • 1
  • 1
jeron-diovis
  • 788
  • 1
  • 8
  • 19

1 Answers1

2

You can use "--save" or "--save-dev" when you install and resolve these conflicts - in this way, bower will update accordingly the json file. Next time when you run bower install, bower will read the written sections and will not ask you any more.

No need for manual edits - unless you know what you're doing.

Dragos Rusu
  • 1,508
  • 14
  • 14