-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Bump min node/firefox/chrome version to ensure globalThis #25375
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
89714d4
to
b8165d7
Compare
I vividly remember authoring a PR that unconditionally used The caniuse numbers make it seem like it would be ubiquitous, and I do agree that bumping the min browser versions is ok to make this happen; I suppose our test suite should coax out what the issue was before, if one exists. LGTM. |
Prior to this change we were testing on a version of node that didn't include |
This change bumps the minimum versions of these engines so that we no longer need to support engines without `globalThis`.
Maybe as a followup we can see of converting |
This means we no longer need to worry about engines without mutable global support. Followup to emscripten-core#25375.
This means we no longer need to worry about engines without mutable global support. Followup to emscripten-core#25375.
This means we no longer need to worry about engines without mutable global support. Followup to emscripten-core#25375.
This means we no longer need to worry about engines without mutable global support. Followup to emscripten-core#25375.
This means we no longer need to worry about engines without mutable global support. Followup to #25375.
This change bumps the minimum versions of these engines so that we no longer need to support engines without
globalThis
.