Consider making volo a plain npm-installable node package about volo

[jrburke]

cc @dustinboston and @mstade since they have been making some volo commands. I do not think this changes things much, just a different wrapper in the internal volo commands, see the prime branch's commands directory for how they look now.

[sgentile]

I think it's a great idea

[dustinboston]

@jrburke I think it's a great move. I don't really mind using the single file, but there are a lot of nice benefits to using npm. Thanks for the heads up! BTW I've just started using git submodules. Um, they're awesome. I wonder if there would be any benefit to wrapping git add submodule and using git internals to do the updates that we were talking about?

[jrburke]

@dustinboston I hope to replace most submodule use with volo use for front end dependencies. git submodules are awful to deal with, and for the cases where you are just consuming code, not needing to modify it, the submodules junk is more confusing, particularly when you work in a few branches in a tree. By using volo, or npm for that matter and committing the node_modules contents, end consumers do not need to fiddle with git submodules, and it is much clearer what happens when switching branches.

[dustinboston]

@jrburke That makes a lot of sense. Thanks!

[jrburke]

This has been merged to master as of cfd1a9e. A few more fixes for some issues for 0.2 and the 0.2 release will go out with this structure.