content: clarify process.nextTick() timing
#7204
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
avivkeller
reviewed
Nov 13, 2024
apps/site/pages/en/learn/asynchronous-work/understanding-processnexttick.md
Outdated
Show resolved
Hide resolved
KunalKumar-1
force-pushed
the
update_nextTick_timing
branch
from
aa82669 to
97f7bb0
Compare
avivkeller
approved these changes
Nov 16, 2024
AugustinMauroy
approved these changes
Nov 16, 2024
github-actions
bot
removed
the
github_actions:pull-request
Contributor
|
Lighthouse Results
|
Contributor
Unit Test Coverage Report
Unit Test Report
|
bmuenzenmeyer
pushed a commit
that referenced
this pull request
Nov 21, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
Description
fixes: nodejs/node#51871
Updated the explanation of
process.nextTick()to accurately reflect its execution timing in relation to the event loop phases, emphasizing that it runs immediately after the current operation, before moving to the next phase, not after "close callbacks."Validation
Related Issues
Check List
npm run formatto ensure the code follows the style guide.npm run testto check if all tests are passing.npx turbo buildto check if the website builds without errors.