default.js in Next.js — Graceful Fallbacks for Parallel and Dynamic Routes

In Next.js, the default.js file provides a fallback for Parallel Routes when the active state of a slot cannot be recovered after a full-page load. This article explains how to use default.js, access dynamic route parameters, handle catch-all segments, and generate static paths with generateStaticParams.

default.jsParallel RoutesDynamic SegmentsgenerateStaticParams

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

1. What Is default.js?


In Parallel Routes, Next.js preserves the active state of each slot during soft navigation. But after a hard navigation (full-page reload), it cannot recover the active state. In such cases, a default.js file is rendered for unmatched slots.


Example:

When navigating to /settings, the @team slot renders the settings page, but @analytics has no matching route. If default.js is missing, Next.js throws an error.


Manual 404 fallback:

// app/@team/default.js
import { notFound } from 'next/navigation'

export default function Default() {
  notFound()
}

2. Accessing Dynamic Params in default.js


The params prop is a promise. Use async/await or use() to access values.

// app/[artist]/@sidebar/default.js
export default async function Default({ params }) {
  const { artist } = await params
}

3. Dynamic Segments in Next.js


Create dynamic segments by wrapping folder names in square brackets:

// app/blog/[slug]/page.tsx
export default async function Page({ params }) {
  const { slug } = await params
  return <div>My Post: {slug}</div>
}

4. In Client Components


Use use() or useParams() to access dynamic params:

'use client'
import { use } from 'react'

export default function BlogPostPage({ params }) {
  const { slug } = use(params)
  return <p>{slug}</p>
}

5. Catch-all vs Optional Catch-all Segments


  • Catch-all: [...slug] → matches only when params exist
  • Optional Catch-all: [[...slug]] → also matches routes without params

Example:

// app/shop/[[...slug]]/page.js
// /shop → { slug: undefined }
// /shop/clothes → { slug: ['clothes'] }
// /shop/clothes/tops → { slug: ['clothes', 'tops'] }

6. Typing Params in TypeScript


Use PageProps or RouteContext for precise typing. You can also validate values at runtime:

function assertValidLocale(value: string): asserts value is Locale {
  if (!isValidLocale(value)) notFound()
}

7. Using generateStaticParams


Generate static paths at build time:

export async function generateStaticParams() {
  const posts = await fetch('https://.../posts').then(res => res.json())
  return posts.map(post => ({ slug: post.slug }))
}

Fetch calls inside this function are automatically deduplicated to speed up builds.


Conclusion


The default.js file plays a key role in handling Parallel Routes and fallback behavior in Next.js. Combined with dynamic segments, catch-all routing, and static generation, it helps build fast, resilient, and flexible applications.


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

مقالات مرتبط

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.

ادامه