I keep getting an error when writing not-found.js in Next13 (app router)

Question

I wrote not-found.tsx on top of the default file created when create next app. It seems to be working fine, but the console keeps giving me an error every second.

Also, when I run the next app with next dev --turbo, a huge error occurs when accessing localhost:3000/404.

I am now new to next.js. And I am learning App Router. The question that comes to mind while learning is whether this can be applied to a product. I feel like Next.js is too shabby, and as someone who developed only React as a SPA for 4 years, it's very confusing.

sahil manhotra · Accepted Answer · 2023-09-04 19:20:39Z

0

I ended up adding a catch-all route where the 404 was being generated from to return notFound() from it.

Create a folder: e.g. [...404] Create a page.tsx or page.jsx page with the following:

import { notFound } from "next/navigation"
export default function NotFound() {
  return notFound()
}

Full article https://github.com/vercel/next.js/discussions/40000

edited Sep 4, 2023 at 19:20

answered Sep 4, 2023 at 19:11

sahil manhotra

11 bronze badge

Sign up to request clarification or add additional context in comments.

1 Comment

chebread Over a year ago

I'm really sorry, but none of the answers in the link github.com/vercel/next.js/discussions/40000 work properly in Next13.4.19 on Turbopack

Collectives™ on Stack Overflow

I keep getting an error when writing not-found.js in Next13 (app router)

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related