Sign Up for Free

RunKit +

Try any Node.js package right in your browser

This is a playground to test code. It runs a full Node.js environment and already has all of npm’s 400,000 packages pre-installed, including timeout-raf with all npm packages installed. Try it out:

var timeoutRaf = require("timeout-raf")

This service is provided by RunKit and is not affiliated with npm, Inc or the package authors.

timeout-raf v1.1.4

Bare-bones animation-friendly cancelable timeouts via requestAnimationFrame

100% test coverage


Bare-bones animation-friendly cancelable timeouts via requestAnimationFrame

Provides the familiarity of setTimeout, but via requestAnimationFrame. Deferred callbacks can be fired immediately or killed. See "usage" below.

Important to consider

The requestAnimationFrame approach means your callbacks will likely not fire exactly when you originally instructed. If things are running at a smooth 60fps, callbacks should generally fire within 16ms of being told to. Run the tests to see typical results.


Install via npm.

$ npm i timeout-raf


Require the module - it exposes a single factory function (so there's no need to instantiate instances). Call as you would window.setTimeout, passing a callback and duration.

var timeout = require('timeout-raf');

// typical usage; console.log is called after 1s
timeout(function () {
  console.log('1 second later...');
}, 1000);

Passing context as a parameter

You can pass context via an optional third parameter, allowing you to define the context of the callback.

var awesomeObject = {awesome: 'clearly'};

// logs `clearly` after (about) 1 second
timeout(function () {
}, 1000, awesomeObject);

Passing context normally

You can also pass context per usual by binding the callback to any object.

var awesomeObject = {awesome: 'clearly'};

// also logs `clearly` after (about) 1 second
timeout(function () {
}.bind(awesomeObject), 1000);

Killing a timeout

Keep a reference to the timeout and then call its kill() method to prevent it from ever firing its callback.

// never writes to the console...
var to = timeout(function () {
  console.log('I am never heard from again');
}, 1000);



You can tell a timeout to fire its callback at any time earlier than originally requested. Keep a reference to the timeout and call its fire method if you get antsy. The callback will fire immediately, and never again.

// fired after 1 second and never again
var to = timeout(function () {
  console.log('I could only wait a second!');
}, 2000);

timeout(function () {;
}, 1000);


Tests can be run in-browser via npm test.

RunKit is a free, in-browser JavaScript dev environment for prototyping Node.js code, with every npm package installed. Sign up to share your code.
Sign Up for Free