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
Re-generate preset-env fixtures #11016
Re-generate preset-env fixtures #11016
Conversation
Oh nevermind, |
This is not safe, I'll investigate |
bfa4f6d
to
a6c8c64
Compare
a6c8c64
to
0efeb52
Compare
Ok now it looks ok:
|
"proposal-async-generator-functions": "Asynchronous Iterators", | ||
"proposal-object-rest-spread": "object rest/spread properties", | ||
|
||
// We want to apply this prior to unicode regex so that "." and "u" |
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.
I don't think the order of regex-related plugins still matters since they are essentially feature flags now, the regexpu-core
should only run once for every applicable regex.
"proposal-optional-catch-binding": "optional catch binding", | ||
"proposal-optional-chaining": "optional chaining operator (?.)", | ||
"proposal-unicode-property-regex": "RegExp Unicode Property Escapes", | ||
const es5 = { |
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.
Would be good to add a comment here if the key order will impact the plugin execution order of preset-env.
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.
I coulda swore I had a comment about keeping order of the data, but I guess not ¯_(ツ)_/¯
This PR should only re-order the logged plugins. I don't know why GitHub shows more created lines than deleted, but locally the match: