fix: use Reflect API (2016) instead of Object.hasOwn (2021) #7958
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 ↗︎
1 Ignored Deployment
|
Coverage Report
File Coverage
|
||||||||||||||||||||||||||||||||||||||
dwelle
approved these changes
Apr 25, 2024
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.
Use a more stable Reflect API (since 2016 in major browsers) for handling
observedAppState, instead ofObject.hasOwn(since 2021 in major browsers).The next step is possibly polyfilling the APIs (such as Reflect) through
@vitejs/plugin-legacyand it's specifiers https://www.npmjs.com/package/@vitejs/plugin-legacy#polyfill-specifiers.Can I use Reflect? https://caniuse.com/mdn-javascript_builtins_reflect
Fixes #7957