-
Notifications
You must be signed in to change notification settings - Fork 9.6k
core(legacy-javascript): update to target Baseline #16366
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
for (const coreJsVersion of ['2.6.12', '3.40.0']) { | ||
await waitForVariants(); | ||
|
||
for (const coreJsVersion of ['3.40.0']) { |
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.
You're leaving this as a for
loop in case we need to support more corejs versions in the future?
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.
Yeah, v4 is in the works.
// Map, Set, WeakSet, etc. | ||
// collection("Map", | ||
// Currently not used. See create-polyfill-module-data.js | ||
// expression += `|collection\\(${qt(property)},`; |
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.
Sorry I looked through create-polyfill-module-data.js
but I still don't understand why this is unused
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.
done, is it clear now?
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.
ye, thanks
esmodules
as the anchor for "legacy" JS, use Baselinecore-js-compat
. This made it feasible to add many more polyfillsThis audit can now be described as: inform developers when they are polyfilling a feature that is widely supported across all major browsers, and provide an estimate for how much that costs (in terms of bytes / impact on metrics via byte efficiency).