-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
Some JS polyfills should be added to the list of legacy JS #13440
Comments
Thanks for the close attention in this audit. It took me awhile to recall, but we excluded many of these for a reason: #10937 . I hadn't heard of |
BTW, we have a test harness for verifying this stuff: It creates various bundles using core-js@2 and 3 with different options, and snapshots the signals found. The expectation is that we find no signals when bundling withh latest core-js version +
Seems the only signal we giving a false-positive for at the moment is |
Ah, I updated babel too and I see |
That's strange since in the test from the head of this thread you can find I'll take a look at |
|
Obsolete |
It does not look fixed, lighthouse/core/audits/byte-efficiency/legacy-javascript.js Lines 180 to 229 in 97ab394
|
Continuation of #13439.
Let's check what
core-js
modules are not required in engines with ES modules support:=>
In addition to currently detected features, it's:
It should be added to this list.
The text was updated successfully, but these errors were encountered: