# Vercel — Common mistakes with the Next.js App Router and how to fix them

- Company: Vercel (vercel.com)
- Announced: 2024-01-08T13:00:00+00:00
- Category: not stated
- Coverage: not counted
- Announcement: no
- Group: routine
- Source: https://vercel.com/blog/common-mistakes-with-the-next-js-app-router-and-how-to-fix-them
- Record: https://forck.live/items/21017-common-mistakes-with-the-next-js-app-router-and-how-to-fix-them
- Subject: v0 / AI SDK / AI Gateway

Vercel's guide identifies ten common mistakes developers make with the Next.js App Router, such as using Route Handlers unnecessarily with Server Components, misunderstanding static caching of GET Route Handlers, and misplacing Suspense boundaries. It explains how to fix each issue and provides tips for adopting the new App Router model.

## Evidence

Verbatim from https://vercel.com/blog/common-mistakes-with-the-next-js-app-router-and-how-to-fix-them:

> After talking to hundreds of developers and looking at thousands of Next.js repositories, I've noticed ten common mistakes when building with the Next.js App Router. This post will share why these mistakes can happen, how to fix them, and some tips to help you understand the new App Router model.

---

Record: https://forck.live/items/21017-common-mistakes-with-the-next-js-app-router-and-how-to-fix-them
Catalogue: https://forck.live/llms.txt
Current issue: https://forck.live/feed.md