Meteor's reactivity and the Tracker package is a very powerful feature, as it allows event-like behavior to be attached to every function and every template helper. This reactivity is what keeps our interface consistent.
Although we only touched the Tracker package until now, it has a few more properties that we should take a look at.
We already learned how to instantiate a reactive object. We can call new Tracker.Dependency, which can create and rerun dependencies using depend() and changed().
When we are inside a reactive function, we also have access to the current computational object, which we can use to stop further reactive behavior.
To see this in action, we can use our already running timer and create the following reactive function using Tracker.autorun() in our browser's console:
var count = 0;
var someInnerFunction = function(count){
console.log('Running for the '+ count +' time');
if(count === 10)
Tracker.currentComputation...