release 1.1.0 and 1.2.0

[Sam Hauglustaine]

@eiriklv I've tagged 2 more releases which keep backward compatibility.

It would be great if you can also put them on npm with:

git checkout v1.1.0
npm publish

git checkout v1.2.0
npm publish

I've also set up a GitHub action (CI) to run tests on push. You might have received some messages about this.

Some possible future steps:

• Use modern JS syntax and drop old node support.
• Only start the clock when callbacks are registered and stop when all callbacks are removed.
• Handle objects that implement the Iterator protocol and schedule them with setTimeout instead (related to #2 and #4).

This would however change things considerably.

[Eirik L. Vullum]

Great work Sam 👍 I’ve checked npmjs.com - you should have access to publish to npm. Give it a try and report back. - Eirik

…

28. des. 2019 kl. 12:03 skrev Sam Hauglustaine ***@***.***>:  @eiriklv I've tagged 2 more releases which keep backward compatibility. It would be great if you can also put them on npm with: git checkout v1.1.0 npm publish git checkout v1.2.0 npm publish I've also set up a GitHub action (CI) to run tests on push. You might have received some messages about this. Some possible future steps: Use modern JS syntax and drop old node support. Only start the clock when callbacks are registered and stop when all callbacks are removed. Handle objects that implement the Iterator protocol and schedule them with setTimeout instead (related to #2 and #4). This would however change things considerably. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[Sam Hauglustaine]

That worked wonderfully! Thank you!