Building Bulletproof React Components
Most components only work in the happy path but real apps have SSR, hydration, multiple instances, concurrent rendering, portals, transitions, and more. This guide shows how to make components survive in all those cases
Debugging with AI: Can It Replace an Experienced Developer?
Nadia compares AI-driven debugging with traditional debugging across several real-world issues. The article walks through real bugs, compares AI fixes with manual investigation, and explains why “working” fixes are not always correct.
If you wanna get these updates in your inbox every week, just subscribe to the newsletter
📙 Articles / Tutorials / News
Next.js at Enterprise Level
A step-by-step guide to scaling Next.js apps, from defining SLAs and monitoring to using CDNs, better caching, load balancers, Redis, API Gateways, and event-driven systems
Why Google Refuses to Index Your Next.js Site
If your Next.js site loads fast but still won’t get indexed, the problem is often not SEO. This article breaks down how redirects (especially 308s), missing sitemaps, weak canonicals, and hidden Vercel behaviors can confuse Google. It also introduces vercel-seo-audit, a CLI tool to help you see your site the way Googlebot does and fix indexing problems at the root
Go 1.22, SQLite, and Next.js: The "Boring" Backend
A case for choosing simple, stable tools over trendy stacks. The author builds a backend with Go and SQLite, and connects it to a Next.js frontend
React’s ViewTransition Element
This post looks at React <ViewTransition> component. It compares using the browser’s native View Transitions API directly with using React’s built-in version
📦 Projects / Packages / Tools
Announcing TypeScript 6.0 Beta
TypeScript 6.0 is out in beta and acts as a bridge between 5.9 and the upcoming TypeScript 7.0 (which will use a new Go-based compiler). This release focuses on preparing for 7.0, but also ships useful updates like built-in types for Temporal, Map.getOrInsert, and RegExp.escape, plus a new es2025 target
accept-md
A small tool that lets your Next.js app return clean Markdown when a client sends Accept: text/markdown. It works with both App Router and Pages Router. Great for AI crawlers, docs exports, content reuse, and keeping a canonical Markdown version of your content
vS3
vS3 makes it easy to handle S3 storage in your app. It supports pre-signed URLs, encryption, and request validation, so you don’t have to build everything yourself.
eslint-plugin-next-pages-router
A new ESLint plugin focused on the Next.js Pages Router. It checks route comparisons and router.push / router.replace calls against your actual pages/ folder to catch typos and wrong patterns early. It understands dynamic routes, query strings, basePath, and i18n, and even suggests fixes in editors like VS Code
🌈 Related
State of React 2025
The results of 2025 State of React survey have been released. Tl;dr: 2025 was a big and sometimes chaotic year for React. React 19 raised questions about the future of client-side apps, CRA was sunset, and RSC debates continued. SPAs are still strong, AI tools now default to React, and despite the noise, React remains in a very solid place
Radix UI vs Base UI
Radix UI gives you structured, accessible components with strong defaults and a stable API. Base UI takes a lower-level, behavior-first approach, giving you full control over markup, layout, and animations. The post helps you decide which one fits your project and team best
The Too Early Breakpoint
Shows examples from sites like Time and TechCrunch where layouts change too early and look awkward. The author argues for more thoughtful, flexible designs that adapt smoothly across screen sizes instead of switching to the smallest layout too soon
The logo soup problem (and how to solve it)
The post looks at how uneven logo sizes, hidden padding, and dense vs thin designs create visual chaos. Then it walks through a simple math-based approach and presents LogoSoup, a tiny React library that sizes, crops, and aligns logos automatically
Top comments (0)