"매 web platform 의 de-facto reference engine". Chrome 은 Blink rendering + V8 JS + multi-process architecture 의 매 dominant browser (2026 ~65% global share). 매 web standard 의 첫 ship 자, DevTools 의 industry-standard 디버깅 환경, Chromium 의 매 Edge / Brave / Arc / Opera 의 기반.
Application: storage, service worker, cache, manifest
Lighthouse: audit (perf, a11y, SEO, PWA)
Recorder: user flow capture + replay
매 key feature (2026)
WebGPU (stable)
View Transitions API
Speculation Rules (prerender)
Origin Trials (experimental opt-in)
Built-in Gemini Nano (on-device LLM)
WebAssembly GC + Tail Call
매 응용
Web 앱 dev (DevTools).
Extension dev (MV3).
Headless automation (Puppeteer, Playwright).
Performance profiling (Lighthouse CI).
PWA distribution.
💻 패턴
DevTools console snippet
// 모든 image lazy 의 강제
$$('img').forEach(img=>img.loading='lazy');// Performance mark
performance.mark('start');// ... work
performance.mark('end');performance.measure('work','start','end');console.table(performance.getEntriesByName('work'));
언제: DevTools workflow, extension scaffolding, headless automation 의 generation.
언제 X: 매 cross-browser compat 매 critical (Firefox / Safari 의 also test).
❌ 안티패턴
Chrome-only 가정: vendor-prefixed -webkit- API 의 의존 — 매 standard 의 사용.
Manifest V2: deprecated — 매 MV3 + service worker.
DevTools throttling 의 무시: prod 의 slow 3G 시 불상.
console.log 의 prod ship: bundle bloat + privacy — 매 strip plugin.