tRPC End-to-End Type Safe APIs · 课时

在 Next.js 应用路由器中使用 tRPC

将 tRPC 无缝集成到 Next.js 应用路由器中，利用服务器组件高效获取数据。

第 1 / 4 课12 个步骤

在 Next.js 应用路由器中使用 tRPC 是 CoddyKit 上的免费 tRPC End-to-End Type Safe APIs 课时。这是第 1 节课，共 4 节。你可以在下方免费阅读本课时的完整内容 — 然后在浏览器中使用内置代码编辑器和全天候 AI 导师进行实践。这是 tRPC End-to-End Type Safe APIs 学习路径的一部分，你的进度在网页和 CoddyKit 应用中同步。 tRPC End-to-End Type Safe APIs 课程共包含 4 节课。

本课时的部分内容尚未翻译，以英文显示。

tRPC & Next.js App Router

Welcome to a new era of web development with the Next.js App Router! This lesson will guide you through integrating tRPC into this powerful architecture.

The App Router introduces new paradigms like Server Components and Client Components. tRPC helps you maintain end-to-end type safety across these different rendering environments.

Understanding App Router Basics

Before diving into tRPC, let's quickly recap the App Router's core concepts:

Server Components: Rendered on the server, ideal for data fetching and static content. They don't have state or interactivity.
Client Components: Rendered on the client, enabling interactivity, state, and browser APIs. They are marked with 'use client';.

tRPC plays a key role in making data fetching type-safe, regardless of whether you're in a Server or Client Component.

The tRPC App Router Adapter

To integrate tRPC with the Next.js App Router, you'll use the @trpc/next/app-router adapter. This package provides utilities specifically designed for this environment.

It handles the nuances of calling tRPC procedures from both Server Components (direct calls) and Client Components (via React Query hooks).

Server-side tRPC Setup

First, you need to expose your tRPC API routes within the app directory. This typically involves creating a route.ts file (e.g., app/api/trpc/[trpc]/route.ts).

The adapter helps configure your tRPC server to work seamlessly with Next.js API routes, handling incoming requests and routing them to your tRPC procedures.

Data Fetching in Server Components

One of the biggest advantages of the App Router is fetching data directly in Server Components. With tRPC, this means you can call your backend procedures without any client-side JavaScript.

You'll create a special server-side tRPC client that allows you to call procedures directly, similar to calling a function, all while maintaining type safety.

Server Component Fetching Demo

Here's how you can fetch data using tRPC directly inside a Next.js Server Component (e.g., app/page.tsx). Notice there are no hooks used here.

// app/page.tsx (Server Component)
import { createTRPCProxyClient, httpBatchLink } from '@trpc/client';
import type { AppRouter } from '@/server/routers/_app'; // Your backend router type

// Create a server-side tRPC client for direct usage
const serverClient = createTRPCProxyClient<AppRouter>({
  links: [
    httpBatchLink({
      url: 'http://localhost:3000/api/trpc', // Your tRPC API endpoint
    }),
  ],
});

export default async function HomePage() {
  // Fetch data directly in a Server Component
  const greeting = await serverClient.example.hello.query({
    text: 'from Server Component!'
  });

  return (
    <div>
      <h1>{greeting}</h1>
      <p>This content is rendered on the server.</p>
    </div>
  );
}

Client-side tRPC Setup

For Client Components, you'll still need to set up a client-side tRPC provider. This is typically done in your root layout (e.g., app/layout.tsx) by wrapping your app with a 'use client'; component that provides the tRPC client.

This provider makes tRPC's React Query hooks available to all Client Components.

Data Fetching in Client Components

Inside a Client Component, you'll use tRPC's React Query hooks (like useQuery for fetching or useMutation for modifying data) just as you would in a traditional React app.

Remember to mark your component with 'use client'; at the top of the file to ensure it runs on the client.

Client Component Fetching Demo

This example shows a Client Component (e.g., app/client-page/page.tsx) fetching data using tRPC's useQuery hook. This component would be rendered client-side.

// app/client-page/page.tsx (Client Component)
'use client'; // Mark as a Client Component

import { createTRPCReact } from '@trpc/react-query';
import type { AppRouter } from '@/server/routers/_app'; // Your backend router type

// Initialize tRPC client for React hooks
const trpc = createTRPCReact<AppRouter>();

export default function ClientPage() {
  // Use tRPC hooks to fetch data on the client
  const { data, isLoading, error } = trpc.example.hello.useQuery({
    text: 'from Client Component!'
  });

  if (isLoading) return <p>Loading client data...</p>;
  if (error) return <p>Error: {error.message}</p>;

  return (
    <div>
      <h1>{data}</h1>
      <p>This data was fetched client-side with React Query.</p>
    </div>
  );
}

Choosing Server vs. Client Fetching

When should you fetch data in a Server Component versus a Client Component?

Server Components: Ideal for initial data loads, static content, and data that doesn't need client-side re-fetching or interactivity. Reduces client bundle size.
Client Components: Necessary for interactive features, real-time updates, and data that changes based on user input. Utilizes React Query's caching and re-fetching benefits.

Often, a hybrid approach yields the best performance and user experience.

Quick Check: App Router Fetching

You want to fetch initial, non-interactive data for a blog post directly on the server to improve page load performance. Which component type and tRPC usage pattern would be most appropriate?

在交互式课程中回答

Recap: tRPC in App Router

Great job! You've learned how to integrate tRPC with the Next.js App Router.

tRPC provides end-to-end type safety for both Server Components and Client Components.
Use a server-side tRPC client for direct data fetching in Server Components.
Use React Query hooks (via a client-side provider) for interactive data fetching in Client Components.
Choosing between server and client fetching depends on your performance and interactivity needs.

This hybrid approach allows you to build robust, type-safe Next.js applications!

免费开始

用 AI 导师学习 tRPC End-to-End Type Safe APIs — 免费

在浏览器中编写并运行真实代码，获得全天候 AI 导师的即时帮助，并在网页或应用中继续学习。

课程: 10
课程: 40

免费开始学习查看完整课程

常见问题解答

「在 Next.js 应用路由器中使用 tRPC」课时是免费的吗？

是的 — 「在 Next.js 应用路由器中使用 tRPC」的完整文本可在网页上免费阅读。要进行交互式练习（内置代码编辑器和全天候 AI 导师）并解锁 tRPC End-to-End Type Safe APIs 课程的其余内容，请升级到 CoddyKit PRO。 tRPC End-to-End Type Safe APIs 课程共包含 4 节课。

「在 Next.js 应用路由器中使用 tRPC」这节课中我会学到什么？

将 tRPC 无缝集成到 Next.js 应用路由器中，利用服务器组件高效获取数据。你通过在浏览器中直接运行的动手代码来练习 tRPC End-to-End Type Safe APIs，全天候 AI 导师会在你学习这节课的过程中回答你的问题。

学习 tRPC End-to-End Type Safe APIs 需要有经验吗？

无需任何先前经验。CoddyKit 上的 tRPC End-to-End Type Safe APIs 课程适合初学者到高级学习者，你可以从这里开始或从头开始，按照自己的节奏学习。这是第 1 节课，共 4 节。

「在 Next.js 应用路由器中使用 tRPC」课时需要多长时间？

大多数 CoddyKit 课程大约需要 5–10 分钟。每节课都很精短且互动，所以你能稳步进步，并在网页和应用中从离开的地方继续。

我能在这节 tRPC End-to-End Type Safe APIs 课中编写并运行代码吗？

能。每节 tRPC End-to-End Type Safe APIs 课都包含内置代码编辑器，你可以在浏览器中直接编写并运行真实代码，并获得即时 AI 反馈 — 无需本地设置。

此课程中的所有课时

← 返回 tRPC End-to-End Type Safe APIs