-
Notifications
You must be signed in to change notification settings - Fork 16.5k
feat: add support for --no-experimental-global-navigator #47370
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.
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
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
API LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
API LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
API LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
API LGTM
Release Notes Persisted
|
I have automatically backported this PR to "35-x-y", please check out #47416 |
I have automatically backported this PR to "36-x-y", please check out #47417 |
I have automatically backported this PR to "37-x-y", please check out #47418 |
Description of Change
With Node.js v21 starting to support global navigator object, applications that load 3-rd party plugins need to provide a migration timeline for these plugins that relied on the presence of navigator object to detect web environments which would not be the case anymore.
nodejs/node@309c71a
Release Notes
Notes: add support for
--no-experimental-global-navigator
flag