Building Single-Page Applications (SPAs) with Next.js – Client Rendering, Fast Navigation, and Dynamic Data Fetching

Next.js fully supports building SPAs with client-side rendering, fast transitions, and dynamic data fetching. This article explores common patterns for building SPAs using context, SWR, React Query, Server Actions, and shallow routing — while allowing you to progressively adopt server features as your app grows.

SPAClient RenderingSWRReact Query

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

What Is a SPA?


A Single-Page Application (SPA) is an app where all rendering, navigation, and data fetching happen in the browser. There are no full-page reloads — everything is handled by JavaScript.


Why Use Next.js for SPAs?


  • Automatic code splitting and reduced bundle size
  • Fast navigation with next/link and prefetching
  • Start as a SPA and progressively add server features

Data Fetching with Context and use()


Start data fetching in the root layout and pass the Promise to a context provider:

// app/layout.tsx
let userPromise = getUser()

<UserProvider userPromise={userPromise}>
  {children}
</UserProvider>

Then in a client component:

// app/profile.tsx
const { userPromise } = useUser()
const user = use(userPromise)

This pattern enables partial hydration and streaming.


Using SWR in SPAs


With SWR, you can fetch data on the client or server:

// app/layout.tsx
<SWRConfig value={{ fallback: { '/api/user': getUser() } }}>
  {children}
</SWRConfig>

// app/profile.tsx
const { data, error } = useSWR('/api/user', fetcher)

Initial data is prerendered and read by SWR in the browser.


Using React Query


React Query works with Next.js on both client and server, allowing flexible data fetching strategies.


Rendering Only in the Browser


To disable prerendering for a client component:

const ClientOnlyComponent = dynamic(() => import('./component'), {
  ssr: false,
})

Shallow Routing in the Client


To update the URL without reloading the page:

window.history.pushState(null, '', `?sort=asc`)

Then read the value using useSearchParams.


Using Server Actions in Client Components


Call server-side logic directly from the client without creating an API route:

// app/button.tsx
import { create } from './actions'

<button onClick={() => create()}>Create</button>

Static Export (Optional)


Next.js also supports generating a fully static site, which can offer performance advantages over strict SPAs in some cases.


Conclusion


Next.js is a powerful framework for building SPAs — with client-side rendering, fast navigation, and dynamic data fetching. Using context, SWR, React Query, and Server Actions, you can build a flexible, performant, and scalable application.


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

مقالات مرتبط

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.

ادامه

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.

ادامه