<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Nextjs on Gaurav.dev</title><link>/tags/nextjs/</link><description>Recent content in Nextjs on Gaurav.dev</description><generator>Hugo</generator><language>en-US</language><copyright>© 2026 Gaurav. Built with care and clean code.</copyright><lastBuildDate>Thu, 24 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="/tags/nextjs/index.xml" rel="self" type="application/rss+xml"/><item><title>How to Choose a Modern Web Stack Without Regretting It</title><link>/posts/choosing-modern-web-stack/</link><pubDate>Thu, 24 Sep 2026 00:00:00 +0000</pubDate><guid>/posts/choosing-modern-web-stack/</guid><description>&lt;p&gt;The best technology stack is rarely the one with the longest feature list. It is the one your team can operate confidently while the product changes around it.&lt;/p&gt;&#10;&lt;h2 id="start-with-constraints"&gt;Start with constraints&lt;/h2&gt;&#10;&lt;p&gt;Before comparing frameworks, write down the facts: expected traffic, search requirements, real-time behaviour, integrations, compliance, team experience, delivery date, and operating budget. These constraints eliminate more options than a benchmark ever will.&lt;/p&gt;&#10;&lt;p&gt;&lt;strong&gt;Next.js&lt;/strong&gt; is a strong default for content-rich products that also need application behaviour. It offers flexible rendering, a broad React ecosystem, and a straightforward path to full-stack TypeScript. Its flexibility also means the team must be disciplined about caching and server/client boundaries.&lt;/p&gt;</description></item><item><title>A Production Checklist for Next.js Applications</title><link>/posts/nextjs-production-checklist/</link><pubDate>Fri, 18 Sep 2026 00:00:00 +0000</pubDate><guid>/posts/nextjs-production-checklist/</guid><description>&lt;p&gt;A successful &lt;code&gt;next build&lt;/code&gt; proves that the application compiles. It does not prove that the product is ready for real users, crawlers, traffic spikes, or a difficult incident.&lt;/p&gt;&#10;&lt;h2 id="rendering-and-caching"&gt;Rendering and caching&lt;/h2&gt;&#10;&lt;p&gt;Confirm the rendering strategy for every important route. Static content should not become dynamic because a convenience API reads request state. Dynamic pages need explicit cache behaviour, and revalidation should match how quickly the underlying data can change. Test authenticated and anonymous paths separately.&lt;/p&gt;</description></item><item><title>Next.js, Remix, and the T3 Stack: Three Different Decisions</title><link>/posts/nextjs-remix-t3-stack/</link><pubDate>Wed, 24 Jun 2026 00:00:00 +0000</pubDate><guid>/posts/nextjs-remix-t3-stack/</guid><description>&lt;p&gt;Next.js, Remix, and the T3 Stack are often compared as if they were equivalent products. They are not. Next.js and Remix provide different models for building React applications, while T3 is an opinionated combination of tools—typically Next.js, TypeScript, tRPC, Prisma, and an authentication solution. Understanding that distinction makes the choice much easier.&lt;/p&gt;&#10;&lt;h2 id="nextjs-a-broad-product-platform"&gt;Next.js: a broad product platform&lt;/h2&gt;&#10;&lt;p&gt;Next.js supports static content, server rendering, server components, route handlers, streaming, and client-side interaction within one ecosystem. It is a strong fit when a product combines marketing pages, authenticated application experiences, search visibility, and a large React component ecosystem.&lt;/p&gt;</description></item></channel></rss>