pain point: no control over version resolution

[apaleslimghost]

for projects like design systems that are distributed as multiple modules, being able to control which versions are used is very important. you don't want different components to be able to load e.g. different versions of the buttons component they both depend on, from a visual consistency and a CSS size point of view.

we're currently solving this by using both Bower (so we can force single installed versions) and NPM, which isn't ideal. being able to use a single tool for dependencies would simplify our workflow. this probably goes hand-in-hand with #22 because you might want different resolution strategies for different package sets