Skip to content
This repository has been archived by the owner on Mar 31, 2021. It is now read-only.

Use 'resolutions' option in bower #108

Open
eriktrom opened this issue Dec 9, 2013 · 1 comment
Open

Use 'resolutions' option in bower #108

eriktrom opened this issue Dec 9, 2013 · 1 comment

Comments

@eriktrom
Copy link
Contributor

eriktrom commented Dec 9, 2013

There have been some instances of, particularily when adding a new dependency to bower, where the new dependency and the current dependency(required by thorax, et al) conflict. In this situation bower will pause execution and ask which version you'd like to choose. This becomes a bigger problem when using ensure-installed task inside bower, as bower runs in a sub-process, therefore cli output will not pause and ask.

Using the resolutions flag, like in the example below allows us to choose which version of the dep we want bower to choose(thus avoiding the issue)

  "resolutions": {
    "handlebars": "1.0.0"
  }

I am not sure which version of handlebars will make sense here, i will play with adding some new deps and make sure it works right before making a PR

@eastridge
Copy link
Contributor

@Trombom my preference would be we resolve to the latest. Is that a sane option?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

No branches or pull requests

2 participants