use queueMicrotask instead of setTimeout in browsers to avoid browser throttling #1761
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Since
setTimeout
get throttled by browsers andsetImmediate
doesn't actually exist in any browsers, we should usequeueMicrotask
which works very similarly to the intention ofsetImmediate
.I have an app that uses stanza.io which relies on async's
priorityQueue
. It was found thatpriorityQueue
is getting throttled because of its use ofsetTimeout(fn, 0)
. Most browsers supportqueueMicrotask
, but for those who don't, we will fallback.