Scoped Packages

[hughsk]

Will most likely require a major version bump, but I'd like to get this done soon :)

Let's get rid of sources entirely and stick to a key/value mapping of package scopes -> dependencies:

{
  "aperture": {
    "mango": ["features/mango/*"],
    "flow": ["flow/*"]
  }
}

Such that in your code you might pull in modules like so:

var graph = require('@flow/graph')
var node  = require('@flow/node')

@timoxley what're your thoughts on the above? I feel it's better this way, keeps it clear the a module's not coming from npm and consistent with the soon-to-arrive scoped packages: can allow smaller teams to work as if they had their own on-premise npm without all the maintenance overhead involved, potentially easing the transition down the line too.

If we need to use anything other than the sources property then it might be time to look into an optional aperture.json, but if the config can stay this simple that'd be nice!