0Pricing
tRPC End-to-End Type Safe APIs · レッスン

Next.js App RouterでtRPCを使う

サーバーコンポーネントを活用した効率的なデータ取得を行い、tRPCをNext.js App Routerにシームレスに統合します。

「Next.js App RouterでtRPCを使う」はCoddyKit上の無料tRPC End-to-End Type Safe APIsレッスンです。 これはレッスン1/4です。 下記で完全なレッスンを無料で読むことができます。その後、ブラウザ内の組み込みコードエディタと24時間対応の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!

よくある質問

「Next.js App RouterでtRPCを使う」レッスンは無料ですか？

はい。「Next.js App RouterでtRPCを使う」の完全なテキストはこのウェブで無料で読めます。インタラクティブに演習し（組み込みコードエディタと24時間対応のAIチューター）、tRPC End-to-End Type Safe APIsコースの残りをアンロックするには、CoddyKit PROにアップグレードしてください。 tRPC End-to-End Type Safe APIsコースには全4レッスンが含まれています。

「Next.js App RouterでtRPCを使う」で何を学びますか？

サーバーコンポーネントを活用した効率的なデータ取得を行い、tRPCをNext.js App Routerにシームレスに統合します。 ブラウザで直接実行するハンズオンコードでtRPC End-to-End Type Safe APIsを演習し、24時間対応のAIチューターがレッスンを進める中での質問に答えます。

tRPC End-to-End Type Safe APIsを始めるのに経験は必要ですか？

事前経験は必要ありません。CoddyKitのtRPC End-to-End Type Safe APIsは初級者から上級者向けに構成されているため、ここから始めるか最初から始めて、自分のペースで進むことができます。 これはレッスン1/4です。

「Next.js App RouterでtRPCを使う」レッスンにはどのくらい時間がかかりますか？

ほとんどのCoddyKitレッスンは約5～10分かかります。各レッスンはコンパクトでインタラクティブなので、着実に進歩し、ウェブとアプリ全体で正確に前回の場所から再開できます。

このtRPC End-to-End Type Safe APIsレッスンでコードを書いて実行できますか？

はい。すべてのtRPC End-to-End Type Safe APIsレッスンに組み込みコードエディタが含まれているため、ブラウザでリアルコードを書いて実行し、即座のAIフィードバックを取得できます。ローカル設定は不要です。

このコースのすべてのレッスン

  1. Next.js App RouterでtRPCを使う
  2. React Queryの高度な統合
  3. サーバーコンポーネントとtRPCによるデータ取得
  4. tRPCミューテーションの楽観的更新
← tRPC End-to-End Type Safe APIsに戻る