nextjs - 💡(How to fix) Fix `global-not-found` page not used for `notFound()` in root layout [2 comments, 3 participants]

TL;DR

• The issue can likely be resolved by correctly configuring the getStaticPaths or getServerSideProps functions in Next.js to handle 404 routes and serve the global-not-found page.

Guidance

• Review the Next.js documentation on custom 404 pages to ensure that the global-not-found page is properly set up and configured.
• Verify that the next.config.js file does not contain any custom configurations that might be overriding the default 404 behavior.
• Check the file structure and naming conventions to ensure that the global-not-found page is in the correct location and named correctly according to Next.js conventions.
• Test the application with different routes to see if the issue is specific to certain URLs or if it's a global problem.

Example

No specific code example can be provided without modifying the original codebase, but ensuring that the pages directory contains a 404.js or _app.js with the correct import and rendering of the global-not-found component is crucial.

Notes

The provided information does not include the actual code for the global-not-found page or the Next.js configuration, making it difficult to provide a precise fix. However, following Next.js guidelines for custom 404 pages should resolve the issue.

Recommendation

• Apply workaround: Configure the getStaticPaths or getServerSideProps functions correctly to handle 404 routes, as this seems to be the most direct approach to resolving the issue given the information provided.