Browser internals·Advanced·Conceptual·1 min read
What's the risk of calling skipWaiting() unconditionally on every deploy?
Short interview answer
It forces the new worker to activate immediately and take over open tabs, which can serve page HTML from one version alongside JS or CSS from a newer cached version if the page doesn't also reload, producing version-mismatch bugs; many apps instead prompt the user to refresh once an update is detected.
Key takeaway
Explain the underlying mental model clearly, then support it with a concrete example and its trade-offs.