How browsers render, HTTP and caching, fetch, CORS and cookies, storage and offline, the web APIs worth knowing by name.
Pages
- How browsers renderFrom bytes to pixels — parsing and the preload scanner, render-blocking CSS and script loading attributes, the style-layout-paint-composite pipeline, the frame budget, layout thrashing, the observer APIs, long tasks and INP, and where Web Workers fit.
- HTTP and cachingHTTP/1.1 to HTTP/3, methods and status codes worth knowing, and caching as the biggest lever you control — Cache-Control directives, validators and 304s, Vary, CDN behaviour, immutable hashed assets, stale-while-revalidate, resource hints, early hints and speculation rules.
- Fetch, CORS and cookiesWhat fetch does and does not do, credentials and modes, the same-origin policy and how CORS preflights work, why CORS protects users not servers, cross-origin isolation headers, and every cookie attribute — SameSite, Secure, HttpOnly, prefixes, partitioning — with how Nuxt reads and sets them on both sides.
- Storage and offlineThe browser storage options and their quotas, eviction and SSR constraints — Web Storage, IndexedDB, the Cache API, OPFS — plus service workers and their update lifecycle, PWA installability, Web Workers and cross-tab communication, and what "offline-first" actually commits you to.
- Web APIs worth knowing by nameThe platform APIs a senior frontend engineer should be able to reach for without searching — URL and encoding, Web Crypto, files and blobs, history and the Navigation API, View Transitions, Page Lifecycle and bfcache, the Performance and observer APIs, Speculation Rules, clipboard and share, Web Components and WebAssembly — with the questions each one answers.
Notes for the whole section