core(legacy-javascript): remove Object.getOwnPropertyNames signal #13442
Conversation
This file contains 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
connorjclark
commented
Nov 29, 2021
| @@ -1,12 +1,11 @@ | |||
| all-legacy-polyfills | |||
| 84149 all-legacy-polyfills-core-js-3/main.bundle.min.js | |||
| 55778 all-legacy-polyfills-core-js-2/main.bundle.min.js | |||
| 103989 all-legacy-polyfills-core-js-3/main.bundle.min.js | |||
There was a problem hiding this comment.
The cost of polyfilling has increased. So it goes.
adamraine
approved these changes
Nov 29, 2021
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.
I bumped
core-jsin the verification tool from3.9.1to3.19.1, which revealed that we must remove the signal forObject.getOwnPropertyNamesasesmodules: truenow includes it.