Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I would like to complain a bit. The approach in this repository where so many packages are
imply
ed, makes it really hard to reuse this system with other Meteor packages: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 becauseorionjs:core
impliesorionjs:base
which impliesblaze-html-templates
. Why it has to imply it and not just depend on it? This makes it problematic for users who would like to swaptemplating
with Blaze Components and get also server side rendering.