99 Ways to Take Away Your Ugly Polyfills
summary
Distinguishes shims from polyfills and gives concrete fixes: use @babel/preset-env with useBuiltIns: "usage" or the entry import pattern together with core-js and regenerator-runtime so only needed helpers and generators are included. Shows runtime delivery via polyfill.io and a server-side strategy that serves three user-agent–specific bundles (modern, intermediate, and full legacy/IE) to cut client payloads for about 95% of users while still covering IE, reporting reduced typical download sizes.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 0:27Shims vs polyfills
- 1:10Why polyfills needed
- 2:15Babel with polyfills
- 3:17Polyfill browser issues
- 3:38Babel-plugin-compact solution
- 4:43Core-js advantages
- 5:24Babel useBuiltIns & corejs
- 6:08Babel options demo
- 7:31Dynamic polyfill downsides
- 8:56Bund-utils optimization
- 9:39Bund-utils performance
- 10:00Summary & links
related talks
45mRefactoring the polyfills recipe
47mOptimize the frontend by running your own polyfill.io server
27mCompile Like It's 2017
53mPolyfilling the gaps
36m@babel/core: "7.x"
58m10KB or Bust: The Delicate Power of Webpack and Babel
03mMoving JS from Libraries to Polyfills
20mMoving JS from Libraries to Polyfills
