Tag
24 articles tagged #React.
P.01React Router v8 shipped as a deliberately boring release. What the version bump requires, what the codemod handles, and the three things that catch teams.
P.02Searches for React 20 keep climbing, but the latest release is 19.2.7. What actually shipped in the 19.2 line, including useEffectEvent, and why.
P.03TC39 is standardizing signals, the reactive pattern already inside Vue, Solid, Angular, and Preact. Years from browsers, but it changes what to build on.
P.04Next.js 16.3 preview added Instant Navigations, giving server-rendered apps the snappy feel of a client-side SPA. What changed, and when to use it.
P.05All three frameworks matured and all three make different tradeoffs. The four questions we use with clients, and why there's no universally right answer.
P.06TanStack Start hit 1.x stable and is closing on Next.js in downloads. An honest comparison: what each is good at, where each falls short, how to decide.
P.07A 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.08SolidJS 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.09Three.js makes WebGL usable. React Three Fiber makes Three.js feel like React. The fastest path to interactive 3D on the web, and how to use it.
P.10TanStack 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.11Redux is overkill for most React apps: Zustand and Jotai cover most state needs with far less boilerplate. Here is when to use each and how they actually work.
P.12Adding 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.13Storybook 8 is faster and easier to configure than it was. More useful is the workflow shift: building in isolation makes components genuinely decoupled.
P.14Client state is easy. Server state, which lives on a backend and changes on its own, is where React apps make a mess. TanStack Query handles it cleanly.
P.15shadcn/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.16EditorPickLearn how to migrate to Next.js 16 with Turbopack as the default bundler, React Compiler integration, and cache components. Step-by-step guide with code examples.
P.17Server 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.18How we built an AI-powered interface that lets non-technical users query any database using plain English, eliminating SQL expertise requirements and democratizing data access.
P.19Remix 3 drops React for a Preact fork and web-standards-first architecture. Here's why this matters, what it means for React developers, and whether the post-React era is truly upon us.
P.20Astro vs Next.js vs Remix. PostgreSQL vs MongoDB. Vercel vs AWS. Every technology choice in your web application has tradeoffs. Here's a practical guide to making the right decisions for your project.
P.21A CVSS 10.0 pre-auth RCE in React Server Components was exploited within two days of disclosure. Here's the patch guidance and what changed.
P.22EditorPickA 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.
P.23Master Next.js App Router with this comprehensive guide covering Server Components, Partial Pre-rendering, typed routes, and the latest features in Next.js 15 and 16.
P.24Step-by-step guide to configuring a complete full-stack development environment with Python, Django backend, and React frontend.