Tutorials covering the frameworks and libraries that shape how modern applications are built — Angular, React, Vue, and the ecosystem tools that surround them. Each chapter is standalone, built around real examples and verified facts.
The previous chapter introduced Progressive Web Apps and the service worker that makes them possible. This chapter goes deeper into the service worker itself: what it is, how it intercepts requests, how Angular’s implementation differs from a hand-written one, and how to debug it when the cache is serving stale content or the update mechanism…
Streaming SSR and progressive hydration are two sides of the same performance strategy. Streaming SSR changes when the server sends HTML: instead of waiting for the entire tree to render and sending one large response, the server sends the shell immediately and streams the slower regions as their data resolves . Progressive hydration changes when…
The <script setup> block is not a runtime feature. It is a compile-time transformation that rewrites the component’s script and template into a standard setup() function, with binding metadata that drives optimized code generation. The transformation has two distinct modes—inline and function—and the choice between them determines how template expressions are rewritten, how refs are…
Every Angular application has a change detection cycle. When something changes — a user clicks a button, an HTTP response arrives, a timer fires — Angular checks whether the data that templates depend on has changed, and if it has, it updates the DOM. The cycle is the engine of the framework. It is also…
Micro-frontends solve an organizational problem, not a technical one. When multiple teams contribute to the same React application, the codebase becomes a coordination bottleneck: a small change in one feature can break an unrelated feature, builds slow down as the bundle grows, and releases require synchronized deployment across every team . Module Federation addresses this…
Vue’s reactivity system is designed to clean up after itself. When a component unmounts, its effect scope stops, its watchers are disposed, and its reactive dependencies are released. The leaks that remain are almost never Vue’s fault. They are caused by code that creates a resource outside the component’s scope—an event listener on window, a…
The previous chapter covered change detection and rendering — the work Angular does while the application is running. This chapter covers the work that happens before the application runs: downloading, parsing, and executing the JavaScript, CSS, and assets that make up the application. A fast application is not just one that renders efficiently. It is…
Accessibility in React is not a separate layer applied after the component is built. It is a property of the component’s markup, and React’s rendering model gives you direct control over that markup. The WAI-ARIA specification defines roles, states, and properties that communicate the purpose and current condition of a UI element to assistive technology…
A Vue monorepo at scale is not a single tool decision. It is a layered architecture: a package manager that handles dependency resolution and workspace linking, and a build system that handles task orchestration, caching, and affected-project detection. The two layers are independent, and the most common production stack combines pnpm workspaces for the first…
The previous chapter covered bundle sizes and the loading techniques that reduce them. This chapter goes deeper into the specific strategies for loading code on demand. Lazy loading is not a single technique. It is a family of strategies: route-level lazy loading with loadComponent and loadChildren, component-level deferral with @defer, and the preloading strategies that…