next.js: Custom 404 not working in Pages Router if `app` directory exists
Link to the code that reproduces this issue
https://github.com/ajmnz/next-custom-404-repro
To Reproduce
- Install deps (
npm i), start the dev server (npm run dev) and navigate tolocalhost:3000 - Follow the instructions shown
Current vs. Expected behavior
I expected Next.js to detect that I’m working with the Pages Router instead of assuming I’m using the App Router just because there’s a directory called app.
When an app directory is present, Next.js will output ○ Compiling /not-found .... If renamed, it will change to ○ Compiling /404 ..., which is the expected behavior.
Verify canary release
- I verified that the issue exists in the latest Next.js canary release
Provide environment information
Operating System:
Platform: darwin
Arch: x64
Version: Darwin Kernel Version 22.6.0: Wed Oct 4 21:25:26 PDT 2023; root:xnu-8796.141.3.701.17~4/RELEASE_X86_64
Binaries:
Node: 20.8.0
npm: 10.1.0
Yarn: 1.22.10
pnpm: N/A
Relevant Packages:
next: 14.0.3
eslint-config-next: N/A
react: 18.2.0
react-dom: 18.2.0
typescript: 5.3.2
Next.js Config:
output: N/A
Which area(s) are affected? (Select all that apply)
Routing (next/router, next/navigation, next/link)
Additional context
I believe the offending release is between 13.3.4 and 13.5.4 (inclusive). I have an app on 13.3.4 with the same setup described (pages router and a directory called app) and custom 404s are working just fine.
About this issue
- Original URL
- State: open
- Created 3 years ago
- Reactions: 33
- Comments: 22
If you will follow the example in the intl https://github.com/amannn/next-intl/blob/main/examples/example-app-router-playground/src/app/not-found.tsx you will see that they are giving a nice way to handle it.
Also, keep in mind that your pages/404 will not be needed, because when you have the app folder, you will also route the 404 there.
Inside the app folder, create a catch-all route and just all the notFound to make sure that you are serving correctly the 404 for all the routes.
So, in order to solve it, what you need to do it to:
Also, as a side note, make sure that you are not calling the notFound() inside the pages/ because it is not supported and you have to use the
For me, even the dynamic pages are correctly handled now using intl, app and pages together.
Above fix has been testes with Next 14.1.4 and next intl 3.11.1
I have the same problem,
not-found.tsxin development mode is not working inside theappfolder in version14.0.1+, but it is working in build/deploy.I can confirm the issue in dev mode, although if you create a production build, it will use the
404.tsx.Bumping this: this issue is not isolated to the dev server, it also occurs in production builds as of
14.0.5-canary.40. Here’s a repro and some observations: https://github.com/jzxhuang/next-404-pages-router-reproappdir contains alayout.tsx, the404.tsxforpages/router is never used.app/api/route.tsand it appears to have the same issueThis is problematic because it makes it difficult to migrate from pages -> app router. Our app does not work with app router at all atm. We want to incrementally migrate while keeping all routes in
pages/including our 404 page. With this issue, we can’t do that at all…UPDATE: Oddly enough, the behaviour is different when deployed on Vercel vs locally. Locally, I’m running
pnpm build && pnpm start. On Vercel though, we see the 404 page from pages/ router served…here is the deploy: https://next-404-pages-router-repro.vercel.app/asldkf
Interestingly, the Vercel build logs seem to indicate that the app router’s “not-found” should be served, so there must be some difference in the Vercel Next.js runtime compared to
next start?The issue is occuring in the canary and 14th release of Next. I made my portfolio with Next 13. Both development and deployed servers are rendering the 404 page (the default one from Next app).
If you have in your pages-router project an “app” directory, then your 404 page will not work. Try to rename an “app” directory to “appxx” and you will see the magic.
I’m having the same issue in my project.
No, this is about using the Pages Router and having a directory called
appwhich should not be picked up as the App Router.