I assume they are aimed at finding stuff no long needed in script type=module compatible browsers.
While that list is pretty exhaustive it misses fetch.
Fetch could be shipped by
https://polyfill.io/v3/polyfill.min.js?features=fetch
or
https://www.npmjs.com/package/isomorphic-fetch
or
https://github.com/github/fetch
etc
What is the motivation or use case for changing this?
Completness of the feature set for detecting legacy javascript.
How is this beneficial to Lighthouse?
It calls out the unnecessary bytes shipped to the browser which doesnt require the polyfill.
Feature request summary the
LegacyJavascript
audit currently checks forcore-js
polyfills. https://github.com/GoogleChrome/lighthouse/blob/master/lighthouse-core/audits/legacy-javascript.js#L166-L245I assume they are aimed at finding stuff no long needed in
script type=module
compatible browsers. While that list is pretty exhaustive it missesfetch
.Fetch could be shipped by
https://polyfill.io/v3/polyfill.min.js?features=fetch
orhttps://www.npmjs.com/package/isomorphic-fetch
orhttps://github.com/github/fetch
etcWhat is the motivation or use case for changing this? Completness of the feature set for detecting legacy javascript.
How is this beneficial to Lighthouse? It calls out the unnecessary bytes shipped to the browser which doesnt require the polyfill.