Tag
59 articles tagged #Frontend.
P.01Qwik skips hydration entirely instead of optimizing it, and Qwik 2.0 makes that model cheaper to use. Here's how resumability actually works, what changed in 2.0, and the real tradeoffs before you pick it for a production app.
P.02@scope lets a CSS rule apply only inside a specific part of the DOM, with a lower bound that excludes nested components. No BEM, no CSS Modules, no Shadow DOM. Here's how the syntax works and where it still falls short.
P.03Chrome and Edge can prerender your next page before a user clicks it, no SPA rewrite required. Here's how the Speculation Rules API actually works, what it costs in wasted requests, and how to ship it safely.
P.04field-sizing: content reached Baseline Newly Available across Chrome, Firefox, and Safari in June 2026. Here's the one-line CSS that replaces the scrollHeight JavaScript hack for auto-growing textareas, and where its limits are.
P.05Yes, you can build browser push notifications yourself with the Push API, Notifications API, and a service worker. No OneSignal, no Firebase. Here's the full working setup, VAPID keys included.
P.06Searches for React 20 are climbing, but the latest release is React 19.2.7. Here's what's actually shipped in the 19.2 line, including useEffectEvent, and why the version-bump rumor keeps circulating anyway.
P.07Trusted Types, the shape() function, and contrast-color() all crossed into Baseline Newly Available status in early 2026, meaning Chrome, Firefox, and Safari all support them. Here's what each one replaces, with working code, and what 'newly available' actually means for your ship date.
P.08Temporal reached TC39 Stage 4 in March 2026 and ships unflagged in Chrome 144, Firefox 139, and Node.js 26. Here's how to actually migrate common Date patterns to Temporal.PlainDate, ZonedDateTime, and Duration, with real code.
P.09Vite 8 replaced its dual esbuild/Rollup setup with Rolldown, a Rust-based bundler, as the default. Here's what actually changed, the real build-time numbers, and how to tell if migrating pays off for your project.
P.10TC39 is standardizing signals as a native JavaScript primitive, the same reactive pattern already inside Vue, Solid, Angular, and Preact. It won't ship in browsers for years, but it changes what's worth building a library around today.
P.11TC39 finalized ECMAScript 2026 with eight proposals at the March 2026 plenary. Temporal gets the headlines, but the rest of the spec (Iterator Helpers, new Set methods, Promise.try, RegExp.escape, and Float16Array) is worth understanding too. Here's what ships and when you can use it.
P.12Angular's enterprise comeback is real. Signals, standalone components, and zoneless change detection have changed what senior Angular skill looks like. Here's how to hire for it.
P.13Svelte 5 runes changed the reactivity model in ways that matter for hiring. The talent pool is small but experienced. Here's how to find, screen, and evaluate Svelte developers.
P.14Next.js 16.3 preview landed June 25 with Instant Navigations — a set of tools that give server-rendered Next.js apps the snappy feel of a client-side SPA. Here's what changed, what it's built on, and when to use it.
P.15The three major frontend frameworks have all matured significantly and all make different tradeoffs. This is how we help clients choose — and why there is no universally right answer.
P.16TanStack Start hit 1.x stable and is now closing in on Next.js in weekly downloads. Here's an honest comparison of both frameworks — what each is good at, where each falls short, and how to make the call for your project.
P.17Frontend developer means different things to different teams. This guide covers the core screen: HTML semantics, CSS fundamentals, Core Web Vitals, and how to test for real skill rather than framework familiarity.
P.18Vue 3 is now the default and the Options API is legacy. This is what a strong Vue developer looks like in 2026, what questions reveal real skill, and what red flags to watch for.
P.19TypeScript is now the default for most web projects, which means the market is full of developers who write TypeScript without understanding it. Here is how to tell them apart.
P.20Svelte 5's runes replace the old magic variable tracking with explicit reactive primitives. A year into production use, here is what changed, what improved, and what surprised us.
P.21A step-by-step guide to screening React developers in 2026 — what to test, what seniority looks like, and the red flags that save you from a bad hire.
P.22SolidJS is not React with a different syntax. It compiles to real DOM operations, skips the virtual DOM entirely, and has a different mental model for reactivity. Here's what that means in practice.
P.23Three.js makes WebGL accessible. React Three Fiber makes Three.js feel like React. Together they're the fastest path to interactive 3D on the web. Here's how to actually use them.
P.24TanStack Router brings full TypeScript inference to URL params, search params, and loader data. Here's what that looks like in practice and when it's worth adopting.
P.25Images are the single biggest factor in Largest Contentful Paint for most sites. AVIF has widespread browser support now. Here's the optimization stack worth using and how to implement it.
P.26XState v5 ships a rewritten API that's smaller, faster, and easier to read than v4. Here's how state machines actually help in production UI, and what the migration looks like.
P.27Alpine.js lets you add dropdown menus, modals, tabs, and form behavior directly in HTML without a build step or a JavaScript framework. Here's when that's exactly what you want.
P.28CSS @layer lets you define explicit ordering between your reset, base, components, and utility styles. Here's how cascade layers work and how they simplify stylesheet architecture.
P.29Redux is overkill for most React apps. Zustand and Jotai cover 90% of real state management needs with a fraction of the boilerplate. Here's when to use each and how they actually work.
P.30Adding multi-language support to a React app is straightforward when you pick the right library for your setup. Here's how react-i18next, next-intl, and Lingui differ, and which fits each project type.
P.31Three headless CMS platforms used by agencies, three different bets on where content management is going. Here's how Sanity, Payload, and Contentful actually compare when you're building for clients.
P.32The Date object has been broken for 30 years. Temporal is its replacement, now shipping in browsers and Node.js. Here's what actually changed and how to use it.
P.33Storybook 8 is faster and less painful to configure than it used to be. More importantly, the workflow shift it enables — building components in isolation — solves real problems on real teams.
P.34WebGPU is now available across Chrome, Firefox, and Safari. It's not just a graphics API. It's a general-purpose GPU compute layer that changes what's possible in a browser tab.
P.35Three different approaches to styling a web application — Tailwind, CSS Modules, and CSS-in-JS libraries — and the team contexts where each one actually makes sense.
P.36Manifest V3 changed how Chrome extensions work. Here's what actually matters for developers building extensions today: service workers, declarativeNetRequest, and the gotchas nobody warns you about.
P.37Three animation options dominate web development right now: CSS, Framer Motion, and GSAP. Here's how to pick the right one for your project and why the native platform is better than you might expect.
P.38Two browser APIs that used to require JavaScript libraries are now available in all major browsers. Here's what the View Transitions API and scroll-driven animations can do, with working code.
P.39Media queries ask 'how wide is the viewport?' Container queries ask 'how wide is my parent?' That shift changes how you think about reusable components.
P.40If your design system needs to work in React, Vue, and a legacy jQuery app simultaneously, Web Components are the only native answer. Lit makes them practical to write.
P.41Figma shipped real AI features at Config 2025 and teams have been using them for nearly a year. Here is what actually works, what still doesn't, and how design workflows at agencies have changed.
P.42Google's crawler runs JavaScript, but not the same way a browser does. The gap between what your JavaScript app renders and what gets indexed is where most SPA SEO problems hide.
P.43PWAs got a second wind when iOS 16.4 unlocked push notifications and iOS 17 improved install behavior. Three years later, the gap between PWA and native is narrow enough to matter.
P.44Vuex was Vue's state management library for years. Pinia replaced it as the official recommendation and changed how Vue apps manage shared state. Here is how Pinia works and where it fits in a Vue 3 application.
P.45Interaction to Next Paint replaced First Input Delay in 2024, and most sites still haven't caught up. INP is harder to optimize because it measures every interaction, not just the first one.
P.46Client state is easy. Server state — data that lives on a backend, changes over time, and needs to stay in sync — is where most React apps make a mess. TanStack Query handles it without ceremony.
P.47CSS Anchor Positioning lets you position one element relative to another using only CSS. No Popper.js, no JavaScript positioning logic, no layout recalculation on scroll. Here's how it works.
P.48Tauri 2.0 added iOS and Android support while keeping what made 1.x compelling: tiny binaries, Rust backend, and native OS webviews instead of a bundled Chromium. Here's how it works and when to use it.
P.49shadcn/ui is now the default starting point for React UIs. Here's what it actually is, why copy-paste beats npm install, and how to use it without accumulating a mess.
P.50Tailwind v4 moves configuration from JavaScript to CSS, drops the content array, and ships a faster engine. Here's what the breaking changes actually mean for a real project migration.
P.51Biome is a Rust-based JavaScript toolchain that handles linting, formatting, and imports in a single binary. We've been running it in production projects since late 2025. Here's what the migration from ESLint and Prettier actually looks like.
P.52EditorPickWe rebuilt a React SPA as a Django + HTMX app. 847KB of JavaScript became 48KB. Here is every pattern, rough edge, and performance win from the migration.
P.53EditorPickWe have built production apps with all three. Here is an honest comparison of Next.js 15, Astro 5, and Remix covering performance, DX, and when to use each.
P.54Server components have gone from React experiment to cross-framework standard. Here is how they work in React, Vue, Astro, and Svelte — and what changes for your apps.
P.55CSS has changed more in the last 2 years than the previous 10. Here is what is production-ready, what to adopt now, and what you can stop using.
P.56Vue 3.6 introduces Vapor Mode, compiling templates directly to DOM operations and skipping the virtual DOM entirely. We break down the benchmarks, the tradeoffs, and what this means for the vdom debate.
P.57Angular 21 ships with signals-based reactivity, zoneless change detection, and a dramatically simplified developer experience. After years of decline, enterprise teams are reconsidering. Here is what changed.
P.58EditorPickFrom AI-first development to meta-frameworks dominance, discover the key trends shaping web development in 2026 and how to stay ahead of the curve.
P.59EditorPickA comprehensive guide to React 19's new features including Server Components, Actions API, React Compiler, and the new hooks that are changing how we build React applications.