Closed nanoo-k closed 9 years ago
That is a good question. I'm not sure if this can be done, but I will check it
Same issue here. Any progress on this?
Same problem on my end. Normally on plain bower install, it will give us to choose which version of package to use. But with sp:bower:install it just throws exception.
I decided against SpBowerBundle, but one solution may be to include a
resolutions
parameter in bower.json
.
{ "dependencies": { "jquery": "2.1.3", "angular": "1.3.15" }, "resolutions": { "angular": "1.3.9", "jquery": "2.1.3" } }
I haven't tried, but I'm guessing SpBowerBundle respects the definitions
under resolutions
. You'll need to figure out which version to resolve to
yourself, but SpBowerBundle might play nice once you do.
On Tue, May 5, 2015 at 6:51 AM, Tokeiito notifications@github.com wrote:
Same problem on my end. Normally on plain bower install, it will give us to choose which version of package to use. But with sp:bower:install it just throws exception.
— Reply to this email directly or view it on GitHub https://github.com/Spea/SpBowerBundle/issues/115#issuecomment-99083427.
You can handle dependency conflicts in the latest master version. I will try to release a new version asap, but I have to clean up some other things first.
I have several packages whose dependencies conflict with each other. Specifically, several are okay with jQuery#2.1 and one requires jQuery#1.11.1. When conflicts like these arise using
bower install
I can choose which version of jQuery to use (and then I include the other jQuery version giving it a different dependency name, something likejquery-1.11.1
), but runningapp/console sp:bower:install
just fails.Is SpBowerBundle able to resolve this?
Here's my output: