Jan Küster

#366 is good without this one. However, I think this one is important for further work towards 3.0 in order to get comprehensible errors during development.

Maybe adding to 2.6 a warning that jquery will be removed soon in 3.0.0 or something

The question is, if we can solve this in a way, that we can have jQuery as a drop-in or weak dependency so users, who still really really need this...

I would argue that modern browsers have stable and proven replacements like queryselector. Handling Dom Element classes, props and events are also now much easier than in the old days....

@faburem this will likely to be breaking in case you use the template-level jQuery selectors, like `this.$` in `onRendered` or inside events. We may replace these with native query selectors...

I think opening Tracker and ReactiveVar to NPM is good, the implementations could get some refreshment but are in general very solid and in my opinion I would always favour...

@damon-t Blaze has not been updated that much since ~3 years and it just runs fine and stable, which is such a great value for a library/framework. However I agree...

I think we can extract the Meteor variables where possible and allow to inject them as dependencies. I will take a look at your fork and see if we can...

@StorytellerCZ should we consider this for 3.0 ?

Thank you @guncebektas for this PR. Please note, that we first need to merge #382 before we can continue to work on the actual migrations. Once it's done I will...