고급 React Query 연동
tRPC와 함께 프리페칭, 무효화, 백그라운드 재조회를 비롯한 React Query의 강력한 기능을 활용합니다.
고급 React Query 연동은(는) CoddyKit의 무료 tRPC End-to-End Type Safe APIs 강의입니다. 이것은 4개 중 2번째 강의입니다. 아래에서 전체 강의를 무료로 읽을 수 있으며, 내장 코드 에디터와 24/7 AI 튜터와 함께 브라우저에서 직접 실습할 수 있습니다. 이 강의는 tRPC End-to-End Type Safe APIs 학습 경로의 일부이며, 진행 상황이 웹과 CoddyKit 앱에 동기화됩니다. tRPC End-to-End Type Safe APIs 강의에는 총 4개의 강의가 포함되어 있습니다.
이 강의의 일부는 아직 번역되지 않았으며 영어로 표시됩니다.
Advanced React Query with tRPC
Welcome! In this lesson, we'll dive into advanced features of React Query that supercharge your tRPC applications.
You'll learn how to optimize user experience and ensure data freshness using powerful techniques like prefetching, query invalidation, and background refetching.
Improving UX with Prefetching
Prefetching is about fetching data before a user explicitly requests it. Imagine a blog list: when a user hovers over a post, you can prefetch the detailed post content.
- Faster Navigation: Reduces loading times when users click a link.
- Smoother Experience: Eliminates loading spinners on subsequent pages.
- Anticipatory UI: Makes your app feel snappier and more responsive.
Prefetching tRPC Queries
React Query's queryClient.prefetchQuery allows you to fetch data and store it in the cache. With tRPC, you access the queryClient via trpc.useUtils().
This example simulates prefetching a list of posts when a component is rendered, perhaps on a homepage before a user clicks "View All Posts."
// A simplified demo for prefetching a tRPC query
// --- Mocks for demonstration purposes ---
const mockQueryClient = {
prefetchQuery: async (queryKey, queryFn) => {
console.log(`Prefetching: ${JSON.stringify(queryKey)}`);
// Simulate API call
const data = await queryFn();
console.log(`Data for ${JSON.stringify(queryKey)} prefetched:`, data);
return data;
}
};
const trpc = {
post: {
list: {
queryFn: async () => {
// In a real app, this would be your tRPC query
return new Promise(resolve => setTimeout(() => {
resolve([{ id: 1, title: 'First Post' }, { id: 2, title: 'Second Post' }]);
}, 100));
}
}
},
useUtils: () => ({
queryClient: mockQueryClient
})
};
// --- End Mocks ---
async function main() {
console.log("Starting prefetch demo...");
// In a React component, you'd call trpc.useUtils()
const utils = trpc.useUtils();
// Prefetch the 'post.list' query
await utils.queryClient.prefetchQuery(
['post', 'list'], // tRPC query key
trpc.post.list.queryFn // The actual fetch function
);
console.log("Prefetching complete. Data is now in cache.");
}
main();Keeping Data Fresh with Invalidation
After you perform an action that changes data on your backend (like creating, updating, or deleting), your client-side cache might become outdated.
Query invalidation tells React Query that certain cached data is "stale" and needs to be refetched the next time it's accessed. This ensures your UI always shows the latest information.
Invalidating After tRPC Mutations
The most common use case for invalidation is after a mutation. When you create a new item, you want the list showing all items to update automatically.
You can use onSuccess callback of useMutation to invalidate related queries.
// A simplified demo for invalidating a tRPC query after a mutation
// --- Mocks for demonstration purposes ---
const mockQueryClient = {
invalidateQueries: (queryKey) => {
console.log(`Invalidating queries matching: ${JSON.stringify(queryKey)}`);
// In a real app, this marks cached data as stale
}
};
const trpc = {
post: {
create: {
mutateFn: async (newPost) => {
console.log(`Creating post: ${newPost.title}...`);
return new Promise(resolve => setTimeout(() => {
console.log("Post created on server.");
resolve({ id: 3, ...newPost });
}, 150));
}
}
},
useUtils: () => ({
queryClient: mockQueryClient
})
};
// Simulate a useMutation hook's logic
async function useCreatePostMutation() {
const utils = trpc.useUtils();
return {
mutateAsync: async (newPost) => {
const result = await trpc.post.create.mutateFn(newPost);
// Invalidate the 'post.list' query to refetch it
utils.queryClient.invalidateQueries(['post', 'list']);
return result;
}
};
}
// --- End Mocks ---
async function main() {
console.log("Starting invalidation demo...");
const { mutateAsync } = await useCreatePostMutation();
await mutateAsync({ title: 'My New Awesome Post' });
console.log("Mutation complete and 'post.list' query invalidated.");
console.log("Next time 'post.list' is fetched, it will be fresh.");
}
main();Targeting Specific Queries
Sometimes you don't want to invalidate all queries of a certain type. You might want to invalidate a specific item, like a single post after it's been updated.
React Query uses query keys to identify cached data. You can invalidate queries based on exact keys or partial matches.
// Demo for granular invalidation
// --- Mocks ---
const mockQueryClient = {
invalidateQueries: (queryKey) => {
console.log(`Invalidating specific queries: ${JSON.stringify(queryKey)}`);
}
};
const trpc = {
post: {
update: {
mutateFn: async (postId, updates) => {
console.log(`Updating post ${postId} with:`, updates);
return new Promise(resolve => setTimeout(() => {
console.log(`Post ${postId} updated.`);
resolve({ id: postId, ...updates });
}, 100));
}
}
},
useUtils: () => ({
queryClient: mockQueryClient
})
};
async function useUpdatePostMutation() {
const utils = trpc.useUtils();
return {
mutateAsync: async (postId, updates) => {
const result = await trpc.post.update.mutateFn(postId, updates);
// Invalidate the specific post query by ID
utils.queryClient.invalidateQueries(['post', 'byId', { id: postId }]);
// You might also invalidate the list if the update affects it
utils.queryClient.invalidateQueries(['post', 'list']);
return result;
}
};
}
// --- End Mocks ---
async function main() {
console.log("Starting granular invalidation demo...");
const { mutateAsync } = await useUpdatePostMutation();
const postIdToUpdate = 123;
await mutateAsync(postIdToUpdate, { title: 'Updated Title' });
console.log(`Queries for post ${postIdToUpdate} and post list invalidated.`);
}
main();Automatic Background Refetching
React Query doesn't just refetch data when you manually invalidate it. It also has smart defaults for background refetching.
When a query becomes "stale" (its staleTime expires), React Query will automatically refetch it in the background under certain conditions, like:
- When a component mounts.
- When the window refocused.
- When the network reconnects.
Customizing Refetch Behavior
You can control when data is considered stale using the staleTime option. By default, staleTime is 0, meaning data is immediately stale.
Setting a staleTime (e.g., 5 * 60 * 1000 for 5 minutes) means data won't be refetched for that duration, even if components remount or the window is refocused, improving performance.
// Demo for configuring staleTime globally
// --- Mocks ---
class QueryClient {
constructor(options = {}) {
this.defaultOptions = options.defaultOptions || {};
console.log("QueryClient initialized with defaultOptions:", this.defaultOptions);
}
// Simplified method to show it would apply options
fetchQuery(queryKey, queryFn, options = {}) {
const effectiveStaleTime = options.staleTime !== undefined
? options.staleTime
: (this.defaultOptions.queries && this.defaultOptions.queries.staleTime !== undefined
? this.defaultOptions.queries.staleTime
: 0); // Default React Query staleTime
console.log(`Fetching ${JSON.stringify(queryKey)} with staleTime: ${effectiveStaleTime}`);
return queryFn(); // Simulate fetch
}
}
// Simulating React Query's QueryClientProvider setup
function QueryClientProvider({ children, client }) {
console.log("QueryClientProvider is setting up the client.");
// In a real React app, 'client' would be available via context
if (typeof children === 'function') {
children(client); // Just call the child function for this demo
}
}
// --- End Mocks ---
async function main() {
console.log("Starting staleTime configuration demo...");
const queryClient = new QueryClient({
defaultOptions: {
queries: {
staleTime: 1000 * 60 * 5, // 5 minutes
refetchOnWindowFocus: false, // Disable refetch on window focus globally
},
},
});
QueryClientProvider({
client: queryClient,
children: async (client) => {
// Simulate a tRPC query being made, which would inherit these options
await client.fetchQuery(['myPost', 1], async () => {
console.log("Simulating a fetch for 'myPost'.");
return { id: 1, title: "Configured Post" };
});
}
});
console.log("QueryClient configured. Queries will respect 5 min staleTime.");
}
main();A Full Workflow Example
Let's imagine a user flow combining these features:
- User lands on a dashboard. We prefetch data for upcoming sections.
- User clicks "Edit Profile." The profile data is already in cache (due to prefetching or a recent fetch).
- User updates their name. A mutation is triggered.
- Upon success, the profile query is invalidated.
- The UI automatically refetches in the background (due to invalidation and perhaps
staleTime: 0on the profile query), showing the new name without a full page reload or manual refresh.
React Query Features Quiz
Consider a tRPC application where you have a list of products and a form to add a new product.
Which combination of React Query features would you use to immediately update the product list after a new product is successfully added?
Summary of Advanced Features
Great job! You've learned how to leverage advanced React Query features to build highly performant and user-friendly tRPC applications.
- Prefetching improves perceived performance by loading data early.
- Query Invalidation ensures data freshness after mutations.
- Background Refetching automatically updates stale data.
These techniques are crucial for professional-grade frontend development. Keep experimenting with them!
자주 묻는 질문
“고급 React Query 연동” 강의는 무료인가요?
네 — “고급 React Query 연동” 전체 내용을 이 웹사이트에서 무료로 읽을 수 있습니다. 인터랙티브하게 실습하려면(내장 코드 에디터와 24/7 AI 튜터), CoddyKit PRO로 업그레이드하면 tRPC End-to-End Type Safe APIs 강의 전체를 잠금 해제할 수 있습니다. tRPC End-to-End Type Safe APIs 강의에는 총 4개의 강의가 포함되어 있습니다.
“고급 React Query 연동”에서 뭘 배우나요?
tRPC와 함께 프리페칭, 무효화, 백그라운드 재조회를 비롯한 React Query의 강력한 기능을 활용합니다. 브라우저에서 직접 실행하는 실습 코드로 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개 중 2번째 강의입니다.
“고급 React Query 연동” 강의는 얼마나 걸리나요?
대부분의 CoddyKit 강의는 약 5~10분이 소요됩니다. 각 강의는 간결하고 인터랙티브하여 꾸준한 진행이 가능하며, 웹과 앱에서 중단한 부분부터 바로 시작할 수 있습니다.
이 tRPC End-to-End Type Safe APIs 강의에서 코드를 작성하고 실행할 수 있나요?
네. 모든 tRPC End-to-End Type Safe APIs 강의에는 내장 코드 에디터가 포함되어 있으므로, 브라우저에서 바로 실제 코드를 작성하고 실행한 후 즉시 AI 피드백을 받을 수 있습니다 — 로컬 설정이 필요 없습니다.
이 강의의 모든 강의
- Next.js App Router와 tRPC
- 고급 React Query 연동
- 서버 컴포넌트와 tRPC 데이터 조회
- tRPC 변경 작업의 낙관적 업데이트