Optimizing third parties in frameworks with DX
summary
Most sites load third‑party scripts and the talk shows concrete risks and fixes: 94.6% of sites use third parties, and a polyfill takeover redirected over 380 sites as an example of supply‑chain failure. The proposed toolchain uses Unhead’s useScript which defaults to no‑referrer, crossorigin=anonymous and fetchpriority=low and defers execution, adds TypeScript typings, SSR support and consent triggers, and Nuxt/Nux script can bundle third‑party code into your build so scripts serve from your own domain in the demo and it works.
AI-written summary · about
chapters (10)
- 0:00Introduction
- 2:29Third parties in web dev
- 9:10Third-party integration issues
- 14:10Security risks
- 21:36Privacy and GDPR
- 26:53Third-party performance
- 33:09Developer experience challenges with third parties
- 38:16Unhead and script for DX
- 41:09Nux script optimizations
- 48:12Future improvements
related talks
14mOptimizing Third-Party Loading in Next.js
10mOptimizing Third-Parties - Nuxt and Chrome Aurora
31mAn introduction to Nuxt Scripts
46mDeep dive into third-party performance
46mChaperones and curfews: minimising 3rd party impact
22mOptimally using third-party services with Next.js
01h 04mJavaScript's Most Wanted
05mThe Performance Of Others