Does Bower's flat resolver require manual resolutions for every transitive version conflict?
Bower installs all dependencies into a single flat bower_components directory, allowing only one version of any package per project. When two direct dependencies declare incompatible semver ranges for the same transitive package, the client-side resolver cannot automatically satisfy both. The documented remedy is to add a resolutions object to bower.json to
bower