v5.0.1 API changes to BeatEvents

Breaking change

Some slight but more useful and clear changes to BeatEvent creation and callbacks.

heart.createEvent now accepts countTo as an option in place of of repeat, and the callbacks are now called with the number of times that event has happened instead of the heart's age.

This makes more sense than before, where the keyword repeat was a bit confusing, and the heartAge as the callback argument was less useful.

Before

heart.createEvent(5, {repeat: 2}, function(heartAge, last){
  console.log('...heart age is', heartAge);
});

Now

heart.createEvent(5, {countTo: 2}, function(count, last){
  console.log('...Has happened', count, 'times');
});

v4.0.1 Keepalive reliability for Node

• Improves reliability of referencing/unreferencing the interval with or without events in queue

v4.0.0 Keeps app alive as needed

With release 4.0.0 there is a (potentially) breaking change, but for the better.

Now a Heart will keep your Node app alive (if you are using Node) if there are events in queue.
Upon the completion of the very last event, the Heart will be unreferenced and your app will exit, as would be expected.

v3.1.5 Better support for browser use

Addresses an issue with importing on browsers.

v3.1.4 Updates reliability of package

Version bump to 3.1.4

v3.1.2

• Bug fix for named events.
• Internal code cleanup.

Published to npm

v3.0.0 Brand New API

revising API, fixing tests, getting ready for new release