perf/no-legacy-javascript

Dlaczego

Transpiling classes, async functions and optional chaining for browsers nobody uses makes bundles larger and slower to run, and polyfills for Baseline features are downloaded by every visitor.

Poprawka

Declare browser targets once (a browserslist query such as baseline widely available, or the bundler's build.target), drop blanket polyfill imports (core-js/stable in the entry), and add a polyfill only for a feature you use that is not in your targets. See fe-tooling for the configuration.

Przykłady

{ "browserslist": ["baseline widely available"] }

Źródła

• Chrome for Developers, Legacy JavaScript insight
• web.dev, Baseline

Przeczytaj w terminalu

npx github:dawidolko/frontend-skills explain perf/no-legacy-javascript