管理服务器状态
探索管理从服务器获取的数据并使其与用户界面保持同步的策略，包括 SWR 或 React Query
管理服务器状态 是 CoddyKit 上的免费 Next.js 15 Fullstack (App Router + Server Actions) 课时。 这是第 3 节课，共 4 节。 你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。 这是 Next.js 15 Fullstack (App Router + Server Actions) 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 Next.js 15 Fullstack (App Router + Server Actions) 课程共包含 4 节课。
本课时的部分内容尚未翻译，以英文显示。
What is Server State?
When building applications, you deal with different kinds of data. Server state refers to data that lives on a remote server, like a list of products, user profiles, or blog posts.
It's distinct from client state, which is data managed purely within your application, such as whether a modal is open or a theme is dark/light.
Challenges of Server State
Managing server state can be tricky because:
- It's Asynchronous: Data isn't instantly available; it takes time to fetch.
- It Can Be Stale: The data on the server might change after you've fetched it.
- Caching is Hard: How do you store fetched data efficiently and know when to refetch?
- Error Handling: Network requests can fail, requiring robust error management.
- Loading States: Users need feedback while data is being fetched.
Introducing SWR & React Query
Libraries like SWR (Stale-While-Revalidate) and React Query (now TanStack Query) are designed specifically to tackle these server state challenges in React applications.
They provide powerful hooks that simplify data fetching, caching, revalidation, and error handling, making your UI more robust and responsive.
Simple Asynchronous Fetch
Before using a library like SWR, fetching data asynchronously often involves manual handling of loading, success, and error states. Here's a basic JavaScript example:
async function fetchData() {
console.log("Fetching data...");
try {
const response = await fetch('https://jsonplaceholder.typicode.com/todos/1');
if (!response.ok) {
throw new Error(`HTTP error! status: ${response.status}`);
}
const data = await response.json();
console.log("Data fetched: ", data.title);
} catch (error) {
console.error("Fetch error: ", error.message);
}
}
fetchData();The useSWR Hook
SWR wraps this fetching logic into a convenient React Hook called useSWR. It automatically provides the data, error, and a loading state (implicitly via data being undefined initially).
You provide a unique key (often the API endpoint) and a fetcher function that makes the actual data request.
import useSWR from 'swr';
const fetcher = url => fetch(url).then(res => res.json());
function UserProfile() {
// The key is '/api/user', the fetcher is our function
const { data, error } = useSWR('/api/user', fetcher);
if (error) return <div>Failed to load user.</div>;
if (!data) return <div>Loading user...</div>;
return <div>Hello, {data.name}!</div>;
}
// In a Next.js app, UserProfile would be rendered
// inside a page component.Smart Caching & Deduping
One of SWR's core features is its intelligent caching. When multiple components request data with the same key, SWR automatically deduplicates these requests, fetching the data only once.
It then shares this cached data across all subscribers, preventing unnecessary network calls and improving performance. This is crucial for large applications.
Stale-While-Revalidate Strategy
SWR's name comes from its Stale-While-Revalidate caching strategy. This means:
- It immediately returns the cached (stale) data to the UI.
- It then sends a request to revalidate (fetch new) data in the background.
- Once new data arrives, it updates the UI.
This provides an instant user experience while ensuring data freshness.
Automatic Revalidation
SWR and React Query automatically revalidate data in several common scenarios, ensuring your UI always reflects the latest server state:
- On Focus: When the browser tab or window regains focus.
- On Reconnect: When the network connection is restored.
- On Interval: You can configure periodic revalidation for frequently changing data.
This significantly reduces the need for manual data refreshing.
Mutating Data & UI Updates
When you perform actions that change server data (e.g., submitting a form to create a new post), you need to update your UI. SWR provides a mutate function to help with this.
You can use mutate to manually revalidate the data associated with a key, or even update the local cache directly for immediate optimistic UI updates.
Server State Check
Which of the following are key benefits of using a library like SWR or React Query for managing server state?
Recap & Next Steps
You've explored the world of server state and learned why it requires special handling compared to client state. Libraries like SWR and React Query are indispensable tools for Next.js developers, simplifying data fetching, caching, revalidation, and error management.
By leveraging these libraries, you can build more performant, reliable, and user-friendly applications with less effort. Keep practicing these concepts to master your data fetching!
常见问题解答
「管理服务器状态」课时是免费的吗？
是的 — 「管理服务器状态」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 Next.js 15 Fullstack (App Router + Server Actions) 课程的其余内容，请升级到 CoddyKit PRO。 Next.js 15 Fullstack (App Router + Server Actions) 课程共包含 4 节课。
「管理服务器状态」这节课中我会学到什么？
探索管理从服务器获取的数据并使其与用户界面保持同步的策略，包括 SWR 或 React Query 你通过在浏览器中直接运行的动手代码来练习 Next.js 15 Fullstack (App Router + Server Actions)，全天候 AI 导师会在你学习这节课的过程中回答你的问题。
学习 Next.js 15 Fullstack (App Router + Server Actions) 需要有经验吗？
无需任何先前经验。CoddyKit 上的 Next.js 15 Fullstack (App Router + Server Actions) 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。 这是第 3 节课，共 4 节。
「管理服务器状态」课时需要多长时间？
大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。
我能在这节 Next.js 15 Fullstack (App Router + Server Actions) 课中编写并运行代码吗？
能。每节 Next.js 15 Fullstack (App Router + Server Actions) 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。