Alternative use case

[texastoland]

I've been considering how this module could become more useful to me. I prefer to maintain my dependencies in JSON and call volo add [-f]:

{
  …
  volo:
    baseDir: "assets/javascripts/vendor"
    dependencies:
      prelude: "prelude-ls#prelude.ls"
}

I think it'd be convenient to migrate client dependencies to my mimosa-config and not have to set volo.baseDir anymore then update them using mimosa import:

exports.config = {
  …
  dependencies:
    prelude: "prelude-ls#prelude.ls"
}

Additionally this new dependencies section could support a field like dependencies.packageManager: volo|bower|component. Then each could be natively supported in mimsosa/libs/modules/dependencies 👍 👎 ?

exports.config = {
  …
  dependencies:
    # using component(1)
    packageManager: "component" # preferred by Brunch
    "gkz/prelude-ls": "*" # no way to grab uncompiled prelude.ls
    # using bower
    packageManager: "bower" # preferred by Yeoman
    "prelude-ls": "latest" # not positive about syntax
}

[dbashford]

Closing this out. At this point I won't be investing much time pushing volo integration forward. It's been feature stuck for over a year. I really just keep it from being non-functional.