doc: clarify async caveats for events.once()#61572
Merged
nodejs-github-bot merged 1 commit intonodejs:mainfrom Feb 12, 2026
Merged
doc: clarify async caveats for events.once()#61572nodejs-github-bot merged 1 commit intonodejs:mainfrom
events.once()#61572nodejs-github-bot merged 1 commit intonodejs:mainfrom
Conversation
nodejs-github-bot
added
doc
lpinca
approved these changes
Jan 30, 2026
Renegade334
added
the
commit-queue
nodejs-github-bot
removed
the
commit-queue
Collaborator
|
Landed in 3b69757 |
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
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.
The current warnings for
events.once()focus heavily onprocess.nextTick().The footgun really appears in any case where sequential
await events.once(...)statements are used, as execution won't resume within the suspended async function until the current call stack has completed, by which point multiple events may have been emitted. This is just as likely to be run into in general execution, rather than withprocess.nextTick()specifically.Refs: #34220