<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Next.js on Kaisekukun</title><link>https://netguide.jp/zh/tags/next.js/</link><description>Recent content in Next.js on Kaisekukun</description><generator>Hugo -- gohugo.io</generator><language>zh</language><copyright>Kaisekukun</copyright><lastBuildDate>Sun, 12 Jul 2026 00:11:25 +0900</lastBuildDate><atom:link href="https://netguide.jp/zh/tags/next.js/index.xml" rel="self" type="application/rss+xml"/><item><title>Next.js 15 New Features and Upgrade 指南: Migrating Your Project</title><link>https://netguide.jp/zh/web/nextjs-15-upgrade-guide/</link><pubDate>Wed, 08 Jul 2026 10:00:00 +0900</pubDate><guid>https://netguide.jp/zh/web/nextjs-15-upgrade-guide/</guid><description>&lt;img src="https://netguide.jp/img/thumbnail/nextjs-15-upgrade-guide-zh.png" alt="Featured image of post Next.js 15 New Features and Upgrade 指南: Migrating Your Project" /&gt;&lt;p&gt;Next.js 15 is officially released, built on React 19 stable. This major update brings a stable Partial Prerendering (PPR) system, a revamped caching strategy, and Turbopack integration for development builds.&lt;/p&gt;
&lt;p&gt;This article walks through the key new features and provides a step-by-step upgrade guide for migrating from Next.js 14.&lt;/p&gt;
&lt;h2 id="1-key-new-功能"&gt;1. Key New 功能
&lt;/h2&gt;&lt;h3 id="native-react-19-support"&gt;Native React 19 Support
&lt;/h3&gt;&lt;p&gt;Next.js 15 fully embraces React 19. Server Components are now stable, and new hooks like &lt;code&gt;use()&lt;/code&gt; and &lt;code&gt;useOptimistic()&lt;/code&gt; work directly within the App Router. Server Actions are also more efficient with improved performance for action-oriented hooks.&lt;/p&gt;</description></item><item><title>Key Points for Performance Optimization in Next.js App Router</title><link>https://netguide.jp/zh/software/nextjs-app-router-optimization/</link><pubDate>Wed, 25 Feb 2026 12:00:00 +0900</pubDate><guid>https://netguide.jp/zh/software/nextjs-app-router-optimization/</guid><description>&lt;img src="https://netguide.jp/img/thumbnail/nextjs-app-router-optimization-zh.png" alt="Featured image of post Key Points for Performance Optimization in Next.js App Router" /&gt;&lt;p&gt;Leveraging React 18 capabilities, &lt;strong&gt;Next.js App Router&lt;/strong&gt; provides a highly performant architecture for building modern web frontends.&lt;/p&gt;
&lt;p&gt;然而, misconfiguring server-client boundaries or caching rules can lead to slow response times. 在本指南中, we explore practical optimization techniques to build blazing-fast Next.js applications.&lt;/p&gt;
&lt;hr&gt;
&lt;h3 id="1-maximize-react-server-components-rsc"&gt;1. Maximize React Server Components (RSC)
&lt;/h3&gt;&lt;p&gt;The primary benefit of the App Router is that all components are Server Components by default. This eliminates large portions of JavaScript from the client-side bundle.&lt;/p&gt;</description></item><item><title>Next.js App Router 基础 and Migration 技巧</title><link>https://netguide.jp/zh/software/nextjs-app-router-basics/</link><pubDate>Sat, 03 Jan 2026 11:00:00 +0900</pubDate><guid>https://netguide.jp/zh/software/nextjs-app-router-basics/</guid><description>&lt;img src="https://netguide.jp/img/thumbnail/nextjs-app-router-basics-zh.png" alt="Featured image of post Next.js App Router 基础 and Migration 技巧" /&gt;&lt;p&gt;Introduced in Next.js 13, the &lt;strong&gt;App Router&lt;/strong&gt; takes a fundamentally different approach to routing and rendering compared to the traditional Pages Router. Now stable and widely adopted, let&amp;rsquo;s break down the basics for those planning to migrate.&lt;/p&gt;
&lt;h2 id="app-router-vs-pages-router"&gt;App Router vs Pages Router
&lt;/h2&gt;&lt;table&gt;
	&lt;thead&gt;
			&lt;tr&gt;
					&lt;th&gt;Feature&lt;/th&gt;
					&lt;th&gt;Pages Router&lt;/th&gt;
					&lt;th&gt;App Router&lt;/th&gt;
			&lt;/tr&gt;
	&lt;/thead&gt;
	&lt;tbody&gt;
			&lt;tr&gt;
					&lt;td&gt;Routing&lt;/td&gt;
					&lt;td&gt;Under &lt;code&gt;pages/&lt;/code&gt;&lt;/td&gt;
					&lt;td&gt;Under &lt;code&gt;app/&lt;/code&gt;&lt;/td&gt;
			&lt;/tr&gt;
			&lt;tr&gt;
					&lt;td&gt;Components&lt;/td&gt;
					&lt;td&gt;Client Component by default&lt;/td&gt;
					&lt;td&gt;&lt;strong&gt;Server Component&lt;/strong&gt; by default&lt;/td&gt;
			&lt;/tr&gt;
			&lt;tr&gt;
					&lt;td&gt;Layouts&lt;/td&gt;
					&lt;td&gt;Manual implementation&lt;/td&gt;
					&lt;td&gt;Nestable &lt;code&gt;layout.js&lt;/code&gt;&lt;/td&gt;
			&lt;/tr&gt;
			&lt;tr&gt;
					&lt;td&gt;Loading&lt;/td&gt;
					&lt;td&gt;Manual implementation&lt;/td&gt;
					&lt;td&gt;Automatic via &lt;code&gt;loading.js&lt;/code&gt;&lt;/td&gt;
			&lt;/tr&gt;
			&lt;tr&gt;
					&lt;td&gt;Data Fetching&lt;/td&gt;
					&lt;td&gt;&lt;code&gt;getServerSideProps&lt;/code&gt;, etc.&lt;/td&gt;
					&lt;td&gt;Direct &lt;code&gt;async&lt;/code&gt; inside components&lt;/td&gt;
			&lt;/tr&gt;
	&lt;/tbody&gt;
&lt;/table&gt;
&lt;h2 id="1-file-based-routing"&gt;1. File-Based Routing
&lt;/h2&gt;&lt;p&gt;Folder structure inside &lt;code&gt;app/&lt;/code&gt; maps directly to URL paths.&lt;/p&gt;</description></item></channel></rss>