-
-
Notifications
You must be signed in to change notification settings - Fork 34.7k
Closed
nodejs/nodejs.org
#2827Labels
docIssues and PRs related to the documentations.Issues and PRs related to the documentations.good first issueIssues that are suitable for first-time contributors.Issues that are suitable for first-time contributors.timersIssues and PRs related to the timers subsystem / setImmediate, setInterval, setTimeout.Issues and PRs related to the timers subsystem / setImmediate, setInterval, setTimeout.
Description
Is your feature request related to a problem? Please describe.
On this url:
At the process.nextTick() section, it says:
We recommend developers use setImmediate() in all cases because it's easier to reason about (and it leads to code that's compatible with a wider variety of environments, like browser JS.)
But this is untrue since setImmediate() isn't supported in "wider variety of environments". Only supported in Edge & IE, but not Chrome, Firefox, Safari (on both desktop and mobile platforms).
- https://developer.mozilla.org/en-US/docs/Web/API/Window/setImmediate
- https://caniuse.com/#feat=setimmediate
Describe the solution you'd like
- remove that last phrase "(and it leads to code that's compatible with a wider variety of environments, like browser JS.)"?
Describe alternatives you've considered
- I think
setTimeoutandwindow.requestAnimationFrameare the nearest alternatives forsetImmediatefor the browser, but I don't know how to phrase it yet
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
docIssues and PRs related to the documentations.Issues and PRs related to the documentations.good first issueIssues that are suitable for first-time contributors.Issues that are suitable for first-time contributors.timersIssues and PRs related to the timers subsystem / setImmediate, setInterval, setTimeout.Issues and PRs related to the timers subsystem / setImmediate, setInterval, setTimeout.