Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Always grab current setImmediate in queueTask #93

Merged
merged 1 commit into from
May 20, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 7 additions & 4 deletions src/lib/scheduling.ts
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,10 @@ function getSetImmediateFromJsdom() {
// transactions are marked as not active when the event loop runs. The next
// tick queue and microtask queue run within the current event loop macrotask,
// so they'd process database operations too quickly.
export const queueTask: (fn: () => void) => void =
globalThis.setImmediate ||
getSetImmediateFromJsdom() ||
((fn: () => void) => setTimeout(fn, 0));
export const queueTask = (fn: () => void): void => {
const setImmediate =
globalThis.setImmediate ||
getSetImmediateFromJsdom() ||
((fn: () => void) => setTimeout(fn, 0));
setImmediate(fn);
};