splitting the core

This is a heavy one. Perhaps the heaviest. Massive changes on mean.js + dislocation of aggregation into a separate module. Currently the module is local, and required by
require('./aggregation')
but frees the mean.js from all the internal variable bindings, and - splits the core!
Expecting a thorough discussion to see how this might fit into the overall mean.io roadmap.
Dear Yonatan,

you're totally right! Now, I'm not sure about the procedure here... Should
I correct my code and generate a new pull request?

Andrija

On Thu, Sep 11, 2014 at 1:26 PM, Yonatan Ellman <notifications@github.com>
wrote:

> In lib/aggregation.js:
>
> > +      weight: weights[file].weight
> > +    });
> > +  }
> > +  aggregated[group][ext].data = _.map(_.sortBy(temp, 'weight'), function(value) {
> > +    return value.data;
> > +  }).join('\n');
> > +}
> > +
> > +function Aggregator(options,libs,debug){
> > +  this.options = options;
> > +  this.libs = libs;
> > +  this.debug;
> > +}
> > +
> > +Aggregator.prototype.addInlineCode = function(ext,data){
> > +  var md5 = crypto.createHash('md5');
>
> ReferenceError: crypto is not defined
> at Aggregator.addInlineCode
> (/tmp/aaa/node_modules/meanio/lib/aggregation.js:58:13)
>
> require('crypto') missing
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/linnovate/mean-cli/pull/36/files#r17415652>.
>