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.

Sign up for GitHub

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

Jump to bottom

fix: Improved understanding of setImmediate and setTimeout output #6994

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

fix: Improved understanding of setImmediate and setTimeout output #6994

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
176a396
fix: improved understanding of setImmediate and setTimeout output
legendAhsan Aug 19, 2024
37a51aa
fix: improved sentences and example
legendAhsan Sep 13, 2024
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: 10 additions & 1 deletion apps/site/pages/en/learn/asynchronous-work/understanding-processnexttick.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -51,4 +51,13 @@ Running before the timeout => number 3
The timeout running last => number 4
```

The exact output may differ from run to run.
The output aforementioned holds true in ES Modules, e.g. mjs files, but keep in mind in CommonJS case, the output may be different:

```bash
legendAhsan marked this conversation as resolved.
Show resolved Hide resolved
Hello => number 1
Running at next tick => number 2
The timeout running last => number 4
Running before the timeout => number 3
```

This is because the execution order of setImmediate and setTimeout is undeterministic in CommonJs.
legendAhsan marked this conversation as resolved.
Show resolved Hide resolved