This packages `imply` way too much

[mitar]

I would like to complain a bit. The approach in this repository where so many packages are implyed, makes it really hard to reuse this system with other Meteor packages:

• https://github.com/orionjs/orion/blob/master/packages/core/package.js#L21
• https://github.com/orionjs/orion/blob/master/packages/base/package.js#L30

It destroys the whole purpose of dependencies by creating one monolithic package you can or cannot use.

For example, it is now impossible to use orionjs:core together with Blaze Components because orionjs:core implies orionjs:base which implies blaze-html-templates. Why it has to imply it and not just depend on it? This makes it problematic for users who would like to swap templating with Blaze Components and get also server side rendering.

[mitar]

Or probably better solution would be that orion:core would not imply orion:base, just depend on it.

[mitar]

This is now a better fix.

[macrozone]

Has this version been published to atmosphere? I ran in the exaclty described problem with BlazeComponents.

Edit: sorry, did not realized, that this PR is not merged yet.

[nicolaslopezj]

This will be fixed in 1.8

[macrozone]

:+1: awesome