fix: avoid setup global dispatcher in advance #4357
+23
−9
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
himself65
force-pushed
the
himself65/2025/07/22/global
branch
3 times, most recently
from
ec78e58 to
18a7803
Compare
himself65
force-pushed
the
himself65/2025/07/22/global
branch
from
18a7803 to
db91409
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This relates to...
Rationale
Changes
lazy setup dispatcher so that lazyLoadUndici in node.js core module won't affect the
globalThisFeatures
Bug Fixes
Fixes: nodejs/node#59012
Breaking Changes and Deprecations
Status