Advanced Client-Side Routing and Performance Hooks in Next.js

Next.js provides a rich set of client-side hooks and caching utilities that empower developers to build dynamic, responsive, and secure applications. From reading route parameters to tracking navigation state and reporting performance metrics, this guide walks you through the most important tools available in the App Router.

useParamsuseRouterupdateTaguseLinkStatus

~3 دقیقه مطالعه · آخرین به‌روزرسانی ۱۰ آبان ۱۴۰۴

1. useParams — Read Dynamic Route Parameters


useParams() lets you access dynamic segments from the current URL inside Client Components.

'use client'
import { useParams } from 'next/navigation'

const params = useParams<{ tag: string; item: string }>()
// URL: /shop/shoes/nike-air-max-97
// params: { tag: 'shoes', item: 'nike-air-max-97' }

2. usePathname — Get the Current Pathname


usePathname() returns the current pathname. Wrap it in a <Suspense> boundary to avoid hydration mismatches during SSR.


3. useSearchParams — Access Query Strings


useSearchParams() returns a read-only URLSearchParams object to read query strings using .get(), .has(), etc.


4. useRouter — Programmatic Navigation


useRouter() enables navigation from within Client Components.

  • push(): Navigate and add to history
  • replace(): Navigate without adding to history
  • refresh(): Re-fetch and re-render the current route
  • prefetch(): Prefetch route data

5. useSelectedLayoutSegment(s) — Read Active Route Segments


Use useSelectedLayoutSegment() or useSelectedLayoutSegments() in Layouts to build breadcrumbs, tabs, or sidebars.


6. useReportWebVitals — Track Performance Metrics


useReportWebVitals() reports metrics like FCP, LCP, and CLS. Use it in a dedicated Client Component imported into your root layout.


7. useLinkStatus — Inline Navigation Feedback


useLinkStatus() tracks the pending state of a <Link> to show subtle UI feedback during navigation.


8. unauthorized — Custom 401 Handling (Experimental)


unauthorized() throws a 401 error and renders unauthorized.tsx. Enable authInterrupts in next.config.js.


9. unstable_cache — Memoize Expensive Operations


unstable_cache() caches results of expensive functions like database queries. Use tags and revalidate for fine-grained control.


10. updateTag — Real-Time Cache Invalidation


updateTag() is used in Server Actions to invalidate cached data immediately after a mutation.


11. unstable_noStore — Opt Out of Caching


unstable_noStore() disables caching and forces dynamic rendering for the current request.


12. unstable_rethrow — Preserve Next.js Error Behavior


Use unstable_rethrow() inside try/catch to preserve behavior of notFound() or redirect().


13. userAgent — Detect Device and Browser Info


Use userAgent() in Route Handlers to detect device type and rewrite URLs accordingly.


Summary Table


Hook / APIPurposeContext
useParams()Read dynamic route paramsClient Components
usePathname()Get current pathnameClient Components
useSearchParams()Read query stringsClient Components
useRouter()Programmatic navigationClient Components
useLinkStatus()Inline feedback for linksClient Components
useReportWebVitals()Report performance metricsClient Components
unauthorized()Custom 401 error handlingServer Components
unstable_cache()Memoize expensive operationsServer Components
updateTag()Invalidate cache after mutationServer Actions
unstable_noStore()Disable cachingServer Components
unstable_rethrow()Preserve error behaviorServer Components
userAgent()Detect device/browser infoRoute Handlers

نوشته و پژوهش‌شده توسط دکتر شاهین صیامی

مقالات مرتبط

Handling Authorization and Caching in Next.js: A Developer’s Guide

Next.js introduces powerful experimental features for access control and smart caching. This guide covers the unauthorized() function for custom 401 handling, unstable_cache for persistent memoization, updateTag for instant cache invalidation, and useLinkStatus for inline navigation feedback. Learn how to use these tools to build secure, performant, and responsive applications.

ادامه

redirect and refresh in Next.js — Smart Redirects and Client Refreshing via Server Actions

The redirect function in Next.js allows you to navigate users to a new route, returning either a 307 or 303 HTTP response depending on context. It works in Server Components, Client Components, Route Handlers, and Server Actions. The refresh function is used exclusively within Server Actions to refresh the client router. This article explains how both functions work, with practical examples and key considerations.

ادامه

NextRequest and NextResponse in Next.js — Managing Cookies, Headers, Redirects, and Rewrites

Next.js extends the native Web Request and Response APIs with NextRequest and NextResponse, offering powerful tools for managing cookies, headers, redirects, rewrites, and JSON responses. These utilities simplify server-side logic and improve control over routing, personalization, and security. This guide walks through their capabilities with practical examples and best practices.

ادامه

headers, ImageResponse, notFound, and permanentRedirect in Next.js — Request Handling, Dynamic Images, Errors, and Redirects

Next.js offers powerful tools for handling HTTP requests and responses in Server Components. The headers function lets you read incoming request headers. ImageResponse allows you to generate dynamic images using JSX and CSS. The notFound function renders a custom 404 page, and permanentRedirect enables permanent redirection to another route. This article explains how to use each feature with practical examples.

ادامه

A Complete Guide to Using metadata and generateMetadata in Next.js

In modern versions of Next.js, managing page metadata is more powerful and intuitive than ever. Metadata is automatically injected into the <head> of your pages and plays a vital role in SEO, social sharing, and user experience. This guide explains the two main ways to define metadata: using the static metadata object and the dynamic generateMetadata function.

ادامه

generateStaticParams in Next.js — Prebuilding Dynamic Routes at Build Time

The generateStaticParams function in Next.js allows you to prebuild dynamic routes at build time instead of rendering them on-demand. It replaces getStaticPaths from the Pages Router and supports single, multiple, and catch-all segments. You can generate routes from the bottom up or top down, and control fallback behavior using dynamicParams. This article explains how to use generateStaticParams with practical examples and configuration tips.

ادامه