npm install --save precurring
Alternatively, the UMD build is available on unpkg:
<script src="https://unpkg.com/precurring/dist/precurring.umd.js"></script>
You can find the library on window.precurring
.
import precurring from 'precurring';
const ping = precurring({
fn: () => fetch('/ping'),
interval: 5000, // fetch every 5 sec
timeout: 20000, // wait 20 sec max (optional)
onSuccess: console.log,
onError: console.error,
});
ping.start();
import precurring from 'precurring';
let counter = 0;
const instance = precurring({
fn: myFunction,
interval: 1000,
onSuccess: console.log,
onError: () => {
if (++counter === 3) {
instance.stop();
}
},
});
instance.start();
Takes an Object with all the properties listed below and returns an Object with start
and stop
methods.
start()
starts the interval of callingfn
repeatedly.stop()
stops it accordingly.
A function returning a Promise. This is a wrapper function over your own logic, which you want to repeatedly call. The value it resolves to is passed to onSuccess
. If it rejects, the error is passed to onError
.
A number in milliseconds between calls of fn
. To be more precise, it is the time between the previous Promise settling, and fn
being called again. Due to the library using setTimeout
, this specified number is not 100% reliable, see accuracy.
A number in milliseconds after which to cancel fn
. Note that this does not actually stop the execution of fn
but instead ignores its return value after it times out. The timeout
value is also subject to the accuracy issues.
Since this value is optional, the default behavior is to wait however long it takes for the Promise returned by fn
to settle.
A callback function which is called with the value that fn
's Promise settles with.
A callback function which is called with whatever fn
's Promise rejects with.
Under the hood, setTimeout
is used throughout this library. Because of how it is implemented, it does not guarantee the execution time of its callback function. Take this explainer from the MDN docs:
Note: The specified amount of time (or the delay) is not the guaranteed time to execution, but rather the minimum time to execution. The callbacks you pass to these functions cannot run until the stack on the main thread is empty.
As a consequence, code like
setTimeout(fn, 0)
will execute as soon as the stack is empty, not immediately. [...]
However, in most cases this is negligible. If you rely on a more accurate implementation, you should look for a different implementation/library.
- David Walsh's JavaScript fetch with Timeout which this library is based on
MIT © Lion Ralfs