tRPC End-to-End Type Safe APIs · 강의

Next.js App Router와 tRPC

서버 컴포넌트를 활용하여 효율적인 데이터 조회를 구현하고 tRPC를 Next.js App Router에 자연스럽게 연동합니다.

레슨 1/412개 단계

Next.js App Router와 tRPC은(는) CoddyKit의 무료 tRPC End-to-End Type Safe APIs 강의입니다. 이것은 4개 중 1번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 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을(를) 배우세요 — 무료

브라우저에서 실제 코드를 작성하고 실행하며, 24/7 AI 튜터로부터 즉각적인 도움을 받고, 웹이나 앱에서 중단한 부분부터 계속 학습하세요.

코스: 10
레슨: 40

무료로 학습 시작 전체 코스 보기

자주 묻는 질문

“Next.js App Router와 tRPC” 강의는 무료인가요?

네 — “Next.js App Router와 tRPC” 전체 내용을 이 웹사이트에서 무료로 읽을 수 있습니다. 인터랙티브하게 실습하려면(내장 코드 에디터와 24/7 AI 튜터), CoddyKit PRO로 업그레이드하면 tRPC End-to-End Type Safe APIs 강의 전체를 잠금 해제할 수 있습니다. 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/7 AI 튜터가 강의를 진행하면서 질문에 답변해줍니다.

tRPC End-to-End Type Safe APIs을(를) 시작하는 데 경험이 필요한가요?

사전 경험은 필요하지 않습니다. CoddyKit의 tRPC End-to-End Type Safe APIs은(는) 초급자부터 고급 학습자까지를 위해 구성되어 있으므로, 여기서 시작하거나 처음부터 시작할 수 있으며 자신의 속도대로 진행할 수 있습니다. 이것은 4개 중 1번째 강의입니다.

“Next.js App Router와 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(으)로 돌아가기