Storing JWT tokens in localStorage, once a common practice for front‑end authentication, now poses severe XSS risks; this article explains the vulnerabilities, compares HttpOnly cookies, BFF with cookies, and Service Worker‑based solutions, and recommends safer strategies for modern web applications.
Storing JWT tokens in localStorage, once a common practice for front‑end authentication, now poses severe XSS risks, prompting developers to adopt more secure methods such as HttpOnly cookies with SameSite protection, BFF‑backed session cookies, or Service Worker‑based token handling, each with trade‑offs.
This guide explains the shift from persistent background scripts to Service Workers in Manifest V3, compares three timer implementation strategies—including chrome.alarms, content‑script intervals, and event‑driven storage checks—and provides best‑practice recommendations for idempotency, logging, deduplication, and state persistence.
This guide explains how to implement reliable scheduled tasks in Chrome extensions under Manifest V3, covering the shift from persistent background scripts to service workers, three practical approaches—including chrome.alarms, content script timers, and event‑driven simulations—plus best‑practice tips for idempotency, logging, and state persistence.
This article details a solution for playing newly added drink videos on Android TV devices by converting large files into HLS streams, using service workers to cache each fragment in IndexedDB, and employing hls.js to enable seamless offline playback while managing memory constraints.
This article explains how to use Service Workers to apply a Stale‑While‑Revalidate caching strategy, detailing the three‑step process, essential APIs, code examples for intercepting and cloning responses, and a complete Express‑based demo to improve first‑visit page performance.
The article shares a developer’s experience migrating two large Webpack projects to Rspack, covering why Rspack was chosen, detailed lessons on TypeScript handling, CSS extraction, service‑worker support, plugin compatibility, CLI differences, performance benchmarks, and future expectations for the Rust‑based bundler.
This article explains how to use Workbox to simplify Service Worker development, covering installation via CLI or CDN, core concepts like caching strategies, route matching, and custom handlers, and provides practical code examples to improve offline support and performance for web applications.
The article explains common front‑end caching methods—including HTTP headers, browser storage, and HTML5 manifests—then provides a comprehensive guide to Service Workers, covering their lifecycle, registration, typical install/activate/fetch handlers, cache‑update strategies, background sync, and integration with Taro via Workbox.
Advanced interception techniques—such as overriding browser APIs, using ServiceWorkers, employing MutationObservers, creating Proxy‑based sandboxes, and configuring server‑side gateways—provide a flexible middle layer for error reporting, request monitoring, micro‑frontend isolation, and remote debugging, while demanding careful adherence to security policies.
This article explains how Progressive Web Apps use Service Workers to provide offline access, installability, push notifications, and responsive layouts, and it walks through registration, caching strategies, dynamic cache management, expiration handling, and practical code examples for robust offline experiences.
This article explains the AVIF image format, its superior compression and quality compared to JPEG and WebP, provides a detailed comparison of image formats, offers conversion tools and command‑line examples, and shows how to integrate AVIF on the client, server, and via JavaScript polyfills for modern web development.
This article explains the fundamentals of Chrome extension development using Manifest V3, covering concepts such as the manifest file, service workers, content scripts, UI pages, and provides step‑by‑step code examples to build a color‑extraction extension.
This article explains what Progressive Web Apps (PWAs) are, outlines their key characteristics such as cross‑device adaptability, fast loading, offline capability, security and installability, and discusses real‑world examples, Chinese market challenges, and the potential of PWA games.
This article examines the landscape of browser‑based development environments, compares popular online IDEs such as CodeSandbox, StackBlitz, CodePen, and VueSFCREPL, outlines their architectural components, highlights their strengths and limitations, and provides concrete code examples of their underlying mechanisms.
This guide details how to implement web push notifications with Firebase, explaining the underlying push principles, step‑by‑step project setup—including service‑worker registration, token management, and message handling for both notification and data payloads—while also addressing common issues such as service‑worker updates, cross‑browser compatibility, and permission management.
This article explains the principles and practical configurations of HTTP forced and negotiated caching, Service Worker lifecycle and caching, HTTP/2 server push, and CDN caching, providing concrete header examples, code snippets, and recommendations for optimal front‑end performance.
This article details the background, architecture, and step‑by‑step performance optimizations—including Packager caching, request reduction, Service‑Worker caching, and Webpack‑style externals—that reduced a CodeSandbox sandbox build from around two minutes to roughly one second.
Alibaba Cloud Security’s front‑end team tackled the “1‑second battle” by redefining performance with the PCP metric and leveraging PWA techniques—service workers, skeleton screens, aggressive code‑splitting, and micro‑frontend architecture—to shrink perceived load times from seconds to sub‑400 ms across eight products.
This article explains the concepts, creation methods, communication APIs, debugging techniques, and typical use cases of ordinary Web Workers, SharedWorkers, and ServiceWorkers, illustrating how they enable multithreaded computation, cross‑tab data sharing, and offline caching to improve web performance and user experience.
This article provides a comprehensive overview of Progressive Web Apps (PWA), covering their concepts, benefits, real-world case studies, implementation steps with Service Workers, App Shell, manifest files, and related JavaScript workers such as Web Workers, Service Workers, and Worklets, while also discussing their development challenges and future prospects.
This article explains why server‑generated URLs with authentication break traditional HTTP caching and then guides readers through three offline‑caching strategies—HTTP strong and negotiated caching, the now‑deprecated Application Cache, and modern Service Workers—providing practical code examples and best‑practice recommendations.
This article examines how to implement offline Web Push notifications in Chrome using Service Workers, covering background, technical concepts such as BrowserId and the Notifications API, step-by-step code for permission handling, key generation, BrowserId retrieval, and server‑side message delivery.
Progressive Web Apps (PWA) are web applications that leverage Service Workers and modern web technologies to deliver native-like functionality, including offline capabilities, push notifications, and home screen installation, enhancing user experience across devices.
This article explains the concept of Progressive Web Apps, compares them with native and traditional web apps, details the implementation of core PWA features such as App Manifest, Service Worker, caching strategies, push notifications, and Workbox best practices, and shares metrics, challenges, and solutions encountered during the Sharee mobile project.
This article explains the fundamentals of HTTP caching, the role of Service Workers, various cache layers (memory, disk, push), cache-control directives, and provides practical code examples to help front‑end developers improve page load speed and reduce server load.
This article presents an in‑depth front‑end performance checklist covering transfer optimizations, script loading strategies, IntersectionObserver lazy loading, critical CSS inlining, resource hints, service‑worker caching, connection‑aware components, and techniques to prevent layout shifts and improve rendering speed.
This article introduces Service Workers as the core technology of progressive web apps, explains their advantages, security constraints, lifecycle events, CacheStorage API usage, various caching strategies, version‑controlled caching with webpack, background synchronization, and demonstrates how to pass data using IndexedDB, all illustrated with complete code examples.
The article explains Progressive Web Apps—offline‑capable, installable web apps built with Service Workers and a manifest.json—detailing their core qualities, installation requirements, and lifecycle, and showcases iQiyi’s PC PWA implementation that caches assets to speed loading, boosts user retention by 9%, and outlines future enhancements such as offline support and push notifications.
The article introduces Rax PWA, a solution built on Rax 1.x that enables lightweight configuration of Progressive Web Apps, detailing SPA routing, code splitting, App Shell, skeleton screens, snapshot rendering, service‑worker caching, SSR support, and manifest generation to dramatically improve mobile web performance and user experience.
This article details how a team of web developers chose Electron to create a cross‑platform PC client for the teaching tool "Classroom Optimization Master", describing the technology stack, successive architectural evolutions, performance improvements, and lessons learned about modular design and hot updates.
This article explains what a Progressive Web App (PWA) is, how Service Workers enable caching of static, dynamic, and HTML resources, and provides practical techniques such as precaching, offline‑package replacement, update strategies, and a webpack plugin to streamline integration for faster first‑screen loads.
This article explains the fundamentals of Progressive Web Apps (PWA), focusing on Service Workers—its architecture, usage restrictions, compatibility, lifecycle stages, practical code examples, and how to simplify implementation with the Workbox framework for offline caching and push notifications.
This article explains the fundamentals of Service Workers, demonstrates common pitfalls with raw SW code, provides a complete SW implementation, introduces Workbox 3 to simplify caching, compares several caching strategies, and shares practical recommendations for optimal PWA performance.
This article explains why traditional H5 pages perform poorly compared to native apps, introduces Progressive Web Apps (PWA) as a solution, details how service workers enable offline caching, presents real‑world performance comparisons, and reviews common cache strategies such as cache‑first, network‑first, stale‑while‑revalidate, cache‑only, and network‑only.
This article explains what Progressive Web Apps are, outlines the ten criteria that define a qualified PWA, discusses related technologies such as Service Workers and Web Workers, and provides guidance for developers to start building their own PWAs.
This article explains how Progressive Web Apps (PWAs) and Accelerated Mobile Pages (AMP) can be combined, compares their strengths and limitations, and provides practical integration patterns such as AMP-as-PWA, AMP-to-PWA, and AMP-in-PWA, including service‑worker setup and shadow‑DOM techniques.
