Prevent interruptAndCheck from delaying too often when delay takes to…

[thejoecode]

…o long

I ran into an issue where Firefox setTimeout(resolve, 0) was taking the majority of the time between interruptAndCheck calls.

performance.now() - current will be greater than globalInterruptionPeriod so it gets called every iteration

As a work around I can greatly increase the globalinterruptionPeriod with something like setInterruptionPeriod(150) - but then other browsers that don't have the slower setTimeout callback will have slower cancellation responses.

Other fixes I considered: have delayNextTick return performance.now() only for setTimout path (code below) or letting users provide a function that gets called back with current and they can either return current or process.now()

export function delayNextTick(current: number): Promise {
return new Promise(resolve => {
// In case we are running in a non-node environment, setImmediate isn't available.
// Using setTimeout of the browser API accomplishes the same result.
if (typeof setImmediate === 'undefined') {
// there is no way to guarantee
setTimeout(() => resolve(performance.now()), 0);
} else {
setImmediate(() => resolve(current));
}
});
}