What is Next.js?

Simple Explanation

Next.js is a React framework that provides routing, rendering, optimization, backend endpoints, and production tooling.

This topic explains where Next.js fits in modern web development and what problem it solves.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, What is Next.js? is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

export default function Page() {
  return <main>Welcome</main>;
}

Example

export default function Page() {
  return <main>Welcome</main>;
}

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Next.js vs React

Simple Explanation

React builds UI components; Next.js adds application routing, rendering, data fetching, optimization, and deployment patterns.

This topic explains where Next.js fits in modern web development and what problem it solves.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Next.js vs React is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

React component + Next.js route file = application page

Example

React component + Next.js route file = application page

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Why Use Next.js?

Simple Explanation

Next.js is used when a React application needs routing, SEO, server rendering, APIs, performance optimization, and production deployment support.

This topic explains where Next.js fits in modern web development and what problem it solves.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Why Use Next.js? is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

Next.js = React + Routing + Rendering + APIs + Optimization

Example

Next.js = React + Routing + Rendering + APIs + Optimization

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Prerequisites

Simple Explanation

Next.js beginners should know HTML, CSS, JavaScript, React basics, Node.js, npm, and TypeScript basics.

This topic explains where Next.js fits in modern web development and what problem it solves.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Prerequisites is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

HTML + CSS + JavaScript + React + Node + npm + TypeScript

Example

HTML + CSS + JavaScript + React + Node + npm + TypeScript

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

App Router vs Pages Router

Simple Explanation

App Router is the modern Next.js routing system using the app directory; Pages Router is the older router using the pages directory.

This topic explains where Next.js fits in modern web development and what problem it solves.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, App Router vs Pages Router is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

app/ -> App Router
pages/ -> Pages Router

Example

app/ -> App Router
pages/ -> Pages Router

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Full Stack Next.js Architecture

Simple Explanation

Full-stack Next.js can include UI routes, server components, server actions, route handlers, database access, authentication, and deployment.

This topic explains where Next.js fits in modern web development and what problem it solves.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Full Stack Next.js Architecture is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

UI -> Server Component -> Server Action / Route Handler -> Database -> Cache -> Response

Example

UI -> Server Component -> Server Action / Route Handler -> Database -> Cache -> Response

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Next.js Use Cases

Simple Explanation

Next.js can build dashboards, websites, e-commerce, blogs, SaaS apps, portals, docs sites, and backend-for-frontend APIs.

This topic explains where Next.js fits in modern web development and what problem it solves.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Next.js Use Cases is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

Marketing site
Dashboard
Blog
E-commerce
Student portal
Admin panel

Example

Marketing site
Dashboard
Blog
E-commerce
Student portal
Admin panel

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Install Node.js and npm

Simple Explanation

Next.js development requires Node.js and a package manager such as npm, pnpm, yarn, or bun.

This topic helps you create, configure, run, and structure a real Next.js project.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Install Node.js and npm is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

node -v
npm -v

Example

node -v
npm -v

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

create-next-app

Simple Explanation

create-next-app creates a new Next.js project with recommended setup options.

This topic helps you create, configure, run, and structure a real Next.js project.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, create-next-app is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

npx create-next-app@latest student-portal

Example

npx create-next-app@latest student-portal

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Run Development Server

Simple Explanation

The development server runs the Next.js app locally with fast refresh.

This topic helps you create, configure, run, and structure a real Next.js project.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Run Development Server is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

npm run dev

Example

npm run dev

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Production Build

Simple Explanation

The production build compiles and optimizes the Next.js application for release.

This topic helps you create, configure, run, and structure a real Next.js project.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Production Build is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

npm run build
npm start

Example

npm run build
npm start

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Project Structure

Simple Explanation

Next.js project structure includes app, public, components, lib, styles, configuration, and package files.

This topic helps you create, configure, run, and structure a real Next.js project.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Project Structure is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

app/
  layout.tsx
  page.tsx
components/
lib/
public/
next.config.ts
package.json

Example

app/
  layout.tsx
  page.tsx
components/
lib/
public/
next.config.ts
package.json

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

app Directory

Simple Explanation

The app directory defines App Router routes, layouts, pages, loading UI, errors, and route handlers.

This topic helps you create, configure, run, and structure a real Next.js project.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, app Directory is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

app/dashboard/page.tsx -> /dashboard

Example

app/dashboard/page.tsx -> /dashboard

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

public Directory

Simple Explanation

The public directory serves static assets such as images, icons, robots.txt, and files from the root URL.

This topic helps you create, configure, run, and structure a real Next.js project.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, public Directory is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

public/logo.png
<Image src="/logo.png" alt="Logo" width={120} height={60} />

Example

public/logo.png
<Image src="/logo.png" alt="Logo" width={120} height={60} />

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

src Directory

Simple Explanation

The optional src directory keeps application code separate from configuration files.

This topic helps you create, configure, run, and structure a real Next.js project.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, src Directory is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

src/app/page.tsx
src/components/Header.tsx

Example

src/app/page.tsx
src/components/Header.tsx

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

package.json Scripts

Simple Explanation

package.json scripts define common commands such as dev, build, start, lint, and test.

This topic helps you create, configure, run, and structure a real Next.js project.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, package.json Scripts is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

npm run dev
npm run build
npm run start

Example

npm run dev
npm run build
npm run start

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

TypeScript in Next.js

Simple Explanation

TypeScript adds static typing to Next.js pages, components, route handlers, and server functions.

This topic helps you create, configure, run, and structure a real Next.js project.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, TypeScript in Next.js is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

type Student = { id: string; name: string };
export default function Page() { return <h1>Students</h1>; }

Example

type Student = { id: string; name: string };
export default function Page() { return <h1>Students</h1>; }

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

ESLint and Formatting

Simple Explanation

Linting checks code quality and catches common mistakes before release.

This topic helps you create, configure, run, and structure a real Next.js project.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, ESLint and Formatting is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

npm run lint

Example

npm run lint

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Environment Variables

Simple Explanation

Environment variables store configuration values outside source code.

This topic helps you create, configure, run, and structure a real Next.js project.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Environment Variables is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

DATABASE_URL="postgres://..."
NEXT_PUBLIC_SITE_NAME="Student Portal"

Example

DATABASE_URL="postgres://..."
NEXT_PUBLIC_SITE_NAME="Student Portal"

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

next.config.js or next.config.ts

Simple Explanation

next.config configures Next.js behavior such as images, redirects, rewrites, output, and experimental options.

This topic helps you create, configure, run, and structure a real Next.js project.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, next.config.js or next.config.ts is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

const nextConfig = { images: { remotePatterns: [] } };
export default nextConfig;

Example

const nextConfig = { images: { remotePatterns: [] } };
export default nextConfig;

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Path Aliases

Simple Explanation

Path aliases make imports shorter and clearer.

This topic helps you create, configure, run, and structure a real Next.js project.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Path Aliases is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

import Header from "@/components/Header";

Example

import Header from "@/components/Header";

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

File-System Routing

Simple Explanation

Next.js creates routes from folders and files inside the app directory.

This topic belongs to the App Router, the modern file-system routing model in Next.js.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, File-System Routing is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

app/about/page.tsx -> /about
app/dashboard/page.tsx -> /dashboard

Example

app/about/page.tsx -> /about
app/dashboard/page.tsx -> /dashboard

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

page.tsx

Simple Explanation

page.tsx defines the UI for a route segment.

This topic belongs to the App Router, the modern file-system routing model in Next.js.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, page.tsx is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

// app/about/page.tsx
export default function AboutPage() { return <h1>About</h1>; }

Example

// app/about/page.tsx
export default function AboutPage() { return <h1>About</h1>; }

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

layout.tsx

Simple Explanation

layout.tsx defines shared UI that wraps pages and child routes.

This topic belongs to the App Router, the modern file-system routing model in Next.js.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, layout.tsx is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

export default function DashboardLayout({ children }: { children: React.ReactNode }) {
  return <section><nav>Menu</nav>{children}</section>;
}

Example

export default function DashboardLayout({ children }: { children: React.ReactNode }) {
  return <section><nav>Menu</nav>{children}</section>;
}

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Root Layout

Simple Explanation

The root layout is required and wraps the entire application.

This topic belongs to the App Router, the modern file-system routing model in Next.js.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Root Layout is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

export default function RootLayout({ children }: { children: React.ReactNode }) {
  return <html lang="en"><body>{children}</body></html>;
}

Example

export default function RootLayout({ children }: { children: React.ReactNode }) {
  return <html lang="en"><body>{children}</body></html>;
}

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

template.tsx

Simple Explanation

template.tsx is similar to layout but creates a new instance for each child route navigation.

This topic belongs to the App Router, the modern file-system routing model in Next.js.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, template.tsx is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

export default function Template({ children }: { children: React.ReactNode }) {
  return <div>{children}</div>;
}

Example

export default function Template({ children }: { children: React.ReactNode }) {
  return <div>{children}</div>;
}

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

loading.tsx

Simple Explanation

loading.tsx shows instant loading UI while route content is loading.

This topic belongs to the App Router, the modern file-system routing model in Next.js.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, loading.tsx is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

export default function Loading() { return <p>Loading dashboard...</p>; }

Example

export default function Loading() { return <p>Loading dashboard...</p>; }

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

error.tsx

Simple Explanation

error.tsx shows UI when an error happens in a route segment.

This topic belongs to the App Router, the modern file-system routing model in Next.js.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, error.tsx is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

"use client";
export default function Error({ reset }: { reset: () => void }) {
  return <button onClick={reset}>Try again</button>;
}

Example

"use client";
export default function Error({ reset }: { reset: () => void }) {
  return <button onClick={reset}>Try again</button>;
}

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

global-error.tsx

Simple Explanation

global-error.tsx handles errors from the root layout or global route boundary.

This topic belongs to the App Router, the modern file-system routing model in Next.js.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, global-error.tsx is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

"use client";
export default function GlobalError() {
  return <html><body>Something went wrong</body></html>;
}

Example

"use client";
export default function GlobalError() {
  return <html><body>Something went wrong</body></html>;
}

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

not-found.tsx

Simple Explanation

not-found.tsx renders when a route or resource is not found.

This topic belongs to the App Router, the modern file-system routing model in Next.js.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, not-found.tsx is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

export default function NotFound() { return <h1>Page not found</h1>; }

Example

export default function NotFound() { return <h1>Page not found</h1>; }

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Route Groups

Simple Explanation

Route groups organize routes without affecting the URL by using parentheses folders.

This topic belongs to the App Router, the modern file-system routing model in Next.js.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Route Groups is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

app/(marketing)/about/page.tsx -> /about
app/(dashboard)/settings/page.tsx -> /settings

Example

app/(marketing)/about/page.tsx -> /about
app/(dashboard)/settings/page.tsx -> /settings

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Dynamic Routes

Simple Explanation

Dynamic routes use bracket folders to match variable URL segments.

This topic belongs to the App Router, the modern file-system routing model in Next.js.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Dynamic Routes is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

app/products/[id]/page.tsx -> /products/123

Example

app/products/[id]/page.tsx -> /products/123

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Catch-All Routes

Simple Explanation

Catch-all routes match multiple URL segments using [...slug].

This topic belongs to the App Router, the modern file-system routing model in Next.js.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Catch-All Routes is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

app/docs/[...slug]/page.tsx -> /docs/a/b/c

Example

app/docs/[...slug]/page.tsx -> /docs/a/b/c

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Optional Catch-All Routes

Simple Explanation

Optional catch-all routes match zero or more segments using [[...slug]].

This topic belongs to the App Router, the modern file-system routing model in Next.js.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Optional Catch-All Routes is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

app/docs/[[...slug]]/page.tsx -> /docs and /docs/a/b

Example

app/docs/[[...slug]]/page.tsx -> /docs and /docs/a/b

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Route Segment Config

Simple Explanation

Route segment config customizes rendering, caching, runtime, and other behavior.

This topic belongs to the App Router, the modern file-system routing model in Next.js.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Route Segment Config is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

export const dynamic = "force-dynamic";
export const revalidate = 60;

Example

export const dynamic = "force-dynamic";
export const revalidate = 60;

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Parallel Routes

Simple Explanation

Parallel routes render multiple independent route sections at the same time.

This topic belongs to the App Router, the modern file-system routing model in Next.js.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Parallel Routes is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

app/dashboard/@analytics/page.tsx
app/dashboard/@team/page.tsx

Example

app/dashboard/@analytics/page.tsx
app/dashboard/@team/page.tsx

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Intercepting Routes

Simple Explanation

Intercepting routes show route content inside another route context, often for modals.

This topic belongs to the App Router, the modern file-system routing model in Next.js.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Intercepting Routes is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

photo grid -> click photo -> modal route overlays current page

Example

photo grid -> click photo -> modal route overlays current page

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Colocation of Files

Simple Explanation

Colocation means keeping components, tests, and utilities near the route that uses them.

This topic belongs to the App Router, the modern file-system routing model in Next.js.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Colocation of Files is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

app/dashboard/components/StatsCard.tsx
app/dashboard/page.tsx

Example

app/dashboard/components/StatsCard.tsx
app/dashboard/page.tsx

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Link Component

Simple Explanation

The Link component enables client-side navigation between routes.

This topic helps users navigate between pages and helps developers design clean URL structure.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Link Component is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

import Link from "next/link";
<Link href="/dashboard">Dashboard</Link>

Example

import Link from "next/link";
<Link href="/dashboard">Dashboard</Link>

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

useRouter

Simple Explanation

useRouter provides imperative navigation in Client Components.

This topic helps users navigate between pages and helps developers design clean URL structure.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, useRouter is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

"use client";
import { useRouter } from "next/navigation";
const router = useRouter();
router.push("/dashboard");

Example

"use client";
import { useRouter } from "next/navigation";
const router = useRouter();
router.push("/dashboard");

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

redirect Function

Simple Explanation

redirect sends users to another route from server-side code.

This topic helps users navigate between pages and helps developers design clean URL structure.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, redirect Function is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

import { redirect } from "next/navigation";
if (!session) redirect("/login");

Example

import { redirect } from "next/navigation";
if (!session) redirect("/login");

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

notFound Function

Simple Explanation

notFound renders the not-found UI when data or route is missing.

This topic helps users navigate between pages and helps developers design clean URL structure.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, notFound Function is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

import { notFound } from "next/navigation";
if (!product) notFound();

Example

import { notFound } from "next/navigation";
if (!product) notFound();

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

params

Simple Explanation

params contain dynamic route segment values.

This topic helps users navigate between pages and helps developers design clean URL structure.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, params is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

export default async function Page({ params }: { params: Promise<{ id: string }> }) {
  const { id } = await params;
  return <p>{id}</p>;
}

Example

export default async function Page({ params }: { params: Promise<{ id: string }> }) {
  const { id } = await params;
  return <p>{id}</p>;
}

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

searchParams

Simple Explanation

searchParams contain query string values from the URL.

This topic helps users navigate between pages and helps developers design clean URL structure.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, searchParams is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

export default async function Page({ searchParams }: { searchParams: Promise<{ q?: string }> }) {
  const { q } = await searchParams;
  return <p>Search: {q}</p>;
}

Example

export default async function Page({ searchParams }: { searchParams: Promise<{ q?: string }> }) {
  const { q } = await searchParams;
  return <p>Search: {q}</p>;
}

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Active Links

Simple Explanation

Active links show which route is currently selected.

This topic helps users navigate between pages and helps developers design clean URL structure.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Active Links is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

"use client";
import { usePathname } from "next/navigation";
const pathname = usePathname();

Example

"use client";
import { usePathname } from "next/navigation";
const pathname = usePathname();

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Breadcrumbs

Simple Explanation

Breadcrumbs show route hierarchy for user navigation.

This topic helps users navigate between pages and helps developers design clean URL structure.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Breadcrumbs is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

Home / Dashboard / Students / Details

Example

Home / Dashboard / Students / Details

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Prefetching

Simple Explanation

Prefetching loads route resources before the user clicks for faster navigation.

This topic helps users navigate between pages and helps developers design clean URL structure.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Prefetching is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

<Link href="/products">Products</Link>

Example

<Link href="/products">Products</Link>

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Navigation Loading UI

Simple Explanation

Loading UI makes route transitions feel responsive, especially for dynamic routes.

This topic helps users navigate between pages and helps developers design clean URL structure.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Navigation Loading UI is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

app/products/[id]/loading.tsx

Example

app/products/[id]/loading.tsx

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Protected Routes

Simple Explanation

Protected routes require authentication or authorization before content is shown.

This topic helps users navigate between pages and helps developers design clean URL structure.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Protected Routes is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

if (!session) redirect("/login");

Example

if (!session) redirect("/login");

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Route Organization

Simple Explanation

Route organization means grouping public, authenticated, admin, and API areas clearly.

This topic helps users navigate between pages and helps developers design clean URL structure.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Route Organization is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

app/(public)/
app/(dashboard)/
app/api/

Example

app/(public)/
app/(dashboard)/
app/api/

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

React Server Components

Simple Explanation

React Server Components render on the server and can access server resources without shipping their code to the client.

This topic explains where code runs: server, client, build time, request time, or streaming.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, React Server Components is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

export default async function ProductsPage() {
  const products = await getProducts();
  return <ProductList products={products} />;
}

Example

export default async function ProductsPage() {
  const products = await getProducts();
  return <ProductList products={products} />;
}

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Client Components

Simple Explanation

Client Components run in the browser and support state, effects, event handlers, and browser APIs.

This topic explains where code runs: server, client, build time, request time, or streaming.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Client Components is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

"use client";
import { useState } from "react";
export default function Counter() {
  const [count, setCount] = useState(0);
  return <button onClick={() => setCount(count + 1)}>{count}</button>;
}

Example

"use client";
import { useState } from "react";
export default function Counter() {
  const [count, setCount] = useState(0);
  return <button onClick={() => setCount(count + 1)}>{count}</button>;
}

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

use client Directive

Simple Explanation

The use client directive marks a file and its imports as part of the client bundle.

This topic explains where code runs: server, client, build time, request time, or streaming.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, use client Directive is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

"use client";
export default function SearchBox() { return <input />; }

Example

"use client";
export default function SearchBox() { return <input />; }

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Server vs Client Decision

Simple Explanation

Server vs Client decision means choosing where a component should run based on data access and interactivity.

This topic explains where code runs: server, client, build time, request time, or streaming.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Server vs Client Decision is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

Server: fetch data, access database
Client: useState, onClick, browser APIs

Example

Server: fetch data, access database
Client: useState, onClick, browser APIs

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Passing Props Between Server and Client

Simple Explanation

Server Components can pass serializable props to Client Components.

This topic explains where code runs: server, client, build time, request time, or streaming.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Passing Props Between Server and Client is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

<ClientChart data={salesData} />

Example

<ClientChart data={salesData} />

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Context Providers

Simple Explanation

Context providers often need to be Client Components when they use client state.

This topic explains where code runs: server, client, build time, request time, or streaming.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Context Providers is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

"use client";
export function ThemeProvider({ children }: { children: React.ReactNode }) {
  return <>{children}</>;
}

Example

"use client";
export function ThemeProvider({ children }: { children: React.ReactNode }) {
  return <>{children}</>;
}

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Suspense

Simple Explanation

Suspense lets parts of the UI wait for async content while showing fallback UI.

This topic explains where code runs: server, client, build time, request time, or streaming.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Suspense is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

import { Suspense } from "react";
<Suspense fallback={<p>Loading...</p>}><SlowComponent /></Suspense>

Example

import { Suspense } from "react";
<Suspense fallback={<p>Loading...</p>}><SlowComponent /></Suspense>

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Streaming

Simple Explanation

Streaming sends UI to the browser in pieces as it becomes ready.

This topic explains where code runs: server, client, build time, request time, or streaming.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Streaming is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

layout renders first -> slow data section streams later

Example

layout renders first -> slow data section streams later

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Static Rendering

Simple Explanation

Static rendering pre-renders content that does not depend on request-time data.

This topic explains where code runs: server, client, build time, request time, or streaming.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Static Rendering is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

export default async function BlogPage() { return <BlogList />; }

Example

export default async function BlogPage() { return <BlogList />; }

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Dynamic Rendering

Simple Explanation

Dynamic rendering happens when content depends on request-time data such as cookies, headers, or uncached data.

This topic explains where code runs: server, client, build time, request time, or streaming.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Dynamic Rendering is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

import { cookies } from "next/headers";
const store = await cookies();

Example

import { cookies } from "next/headers";
const store = await cookies();

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Hydration

Simple Explanation

Hydration attaches browser interactivity to server-rendered HTML for Client Components.

This topic explains where code runs: server, client, build time, request time, or streaming.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Hydration is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

Server HTML -> browser JS -> interactive UI

Example

Server HTML -> browser JS -> interactive UI

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Node.js Runtime

Simple Explanation

Node.js runtime supports many server APIs and is commonly used for Route Handlers and server logic.

This topic explains where code runs: server, client, build time, request time, or streaming.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Node.js Runtime is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

export const runtime = "nodejs";

Example

export const runtime = "nodejs";

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Edge Runtime

Simple Explanation

Edge runtime runs closer to users with a restricted runtime environment.

This topic explains where code runs: server, client, build time, request time, or streaming.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Edge Runtime is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

export const runtime = "edge";

Example

export const runtime = "edge";

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Fetching Data in Server Components

Simple Explanation

Server Components can fetch data directly using async and await.

This topic explains how Next.js loads, caches, mutates, and refreshes data.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Fetching Data in Server Components is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

export default async function Page() {
  const res = await fetch("https://api.example.com/products");
  const products = await res.json();
  return <pre>{JSON.stringify(products, null, 2)}</pre>;
}

Example

export default async function Page() {
  const res = await fetch("https://api.example.com/products");
  const products = await res.json();
  return <pre>{JSON.stringify(products, null, 2)}</pre>;
}

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

fetch API in Next.js

Simple Explanation

Next.js extends fetch behavior with caching and revalidation options depending on the model used.

This topic explains how Next.js loads, caches, mutates, and refreshes data.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, fetch API in Next.js is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

await fetch("https://api.example.com/posts", { next: { revalidate: 60 } });

Example

await fetch("https://api.example.com/posts", { next: { revalidate: 60 } });

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Caching

Simple Explanation

Caching stores results so future requests can be faster and avoid repeated work.

This topic explains how Next.js loads, caches, mutates, and refreshes data.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Caching is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

// cache behavior depends on route and data configuration

Example

// cache behavior depends on route and data configuration

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Cache Components

Simple Explanation

Cache Components let parts of a route use caching behavior with cache-related APIs.

This topic explains how Next.js loads, caches, mutates, and refreshes data.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Cache Components is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

"use cache";
export async function getProducts() { return db.product.findMany(); }

Example

"use cache";
export async function getProducts() { return db.product.findMany(); }

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

cacheLife

Simple Explanation

cacheLife describes cache lifetime profiles for cached work.

This topic explains how Next.js loads, caches, mutates, and refreshes data.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, cacheLife is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

"use cache";
cacheLife("hours");

Example

"use cache";
cacheLife("hours");

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

cacheTag

Simple Explanation

cacheTag labels cached data so it can be refreshed later by tag.

This topic explains how Next.js loads, caches, mutates, and refreshes data.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, cacheTag is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

"use cache";
cacheTag("products");
return getProducts();

Example

"use cache";
cacheTag("products");
return getProducts();

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

revalidateTag

Simple Explanation

revalidateTag marks cached data with a tag as stale so it can refresh.

This topic explains how Next.js loads, caches, mutates, and refreshes data.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, revalidateTag is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

revalidateTag("products");

Example

revalidateTag("products");

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

updateTag

Simple Explanation

updateTag can be used when the next read should fetch fresh data after a user mutation.

This topic explains how Next.js loads, caches, mutates, and refreshes data.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, updateTag is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

updateTag("products");

Example

updateTag("products");

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

revalidatePath

Simple Explanation

revalidatePath refreshes cached content for a path.

This topic explains how Next.js loads, caches, mutates, and refreshes data.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, revalidatePath is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

revalidatePath("/dashboard/products");

Example

revalidatePath("/dashboard/products");

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Dynamic APIs

Simple Explanation

Dynamic APIs such as cookies and headers depend on the incoming request.

This topic explains how Next.js loads, caches, mutates, and refreshes data.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Dynamic APIs is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

const cookieStore = await cookies();
const token = cookieStore.get("token");

Example

const cookieStore = await cookies();
const token = cookieStore.get("token");

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

No Store and Dynamic Data

Simple Explanation

No-store style behavior is used when data must be fresh for every request.

This topic explains how Next.js loads, caches, mutates, and refreshes data.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, No Store and Dynamic Data is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

await fetch("/api/private", { cache: "no-store" });

Example

await fetch("/api/private", { cache: "no-store" });

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Request Memoization

Simple Explanation

Request memoization avoids repeating the same fetch work during one render pass.

This topic explains how Next.js loads, caches, mutates, and refreshes data.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Request Memoization is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

await fetch(url);
await fetch(url);

Example

await fetch(url);
await fetch(url);

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Loading Data from Database

Simple Explanation

Database access should happen on the server, not in Client Components.

This topic explains how Next.js loads, caches, mutates, and refreshes data.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Loading Data from Database is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

export default async function Page() {
  const users = await db.user.findMany();
  return <UserList users={users} />;
}

Example

export default async function Page() {
  const users = await db.user.findMany();
  return <UserList users={users} />;
}

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario

Best Practices

Common Mistakes

Troubleshooting / Debugging Steps

1. Read the exact terminal, browser console, server log, or deployment log error.
2. Check whether the file is in the correct app folder and uses the correct Next.js file convention.
3. Check whether the code is running on the server or in the browser.
4. Run npm run build because production build catches many issues hidden during development.
5. Check environment variables, route params, request data, cache behavior, and permissions before changing business logic.

Practice Exercises

Quick Interview Answer

Reference Links

Avoiding Waterfalls

Simple Explanation

Avoiding waterfalls means starting independent async work early instead of waiting sequentially.

This topic explains how Next.js loads, caches, mutates, and refreshes data.

For beginners, learn this topic by building one real screen. Example: a dashboard, product list, blog post, login page, student profile, admin panel, or API endpoint. Next.js becomes easier when every concept is connected to a real page, folder, route, component, form, data request, or deployment step.

The most important idea in modern Next.js is that not all code runs in the same place. Some code runs on the server, some code runs in the browser, some code runs during build, and some code runs when a request arrives. Understanding this difference helps you avoid many common mistakes.

In real projects, Avoiding Waterfalls is not only a syntax topic. You should explain what problem it solves, where it is placed in the folder structure, how it affects user experience, how it behaves in production, and what can go wrong.

Command / Syntax / Code

const productsPromise = getProducts();
const categoriesPromise = getCategories();
const [products, categories] = await Promise.all([productsPromise, categoriesPromise]);

Example

const productsPromise = getProducts();
const categoriesPromise = getCategories();
const [products, categories] = await Promise.all([productsPromise, categoriesPromise]);

Output / What It Means

Try it Yourself

Example Explained

Business Use Case

Real-Time Scenario