Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error occurred prerendering page "/404" when using concurrentFeatures: true #31126

Closed
saurabhguptarock opened this issue Nov 8, 2021 · 3 comments
Labels
bug Issue was opened via the bug report template. please add a complete reproduction The issue lacks information for further investigation

Comments

@saurabhguptarock
Copy link

What version of Next.js are you using?

12.0.3

What version of Node.js are you using?

14.18.1

What browser are you using?

Chrome

What operating system are you using?

macOS

How are you deploying your application?

Vercel

Describe the Bug

Error occurred prerendering page "/404". Read more: https://nextjs.org/docs/messages/prerender-error
Error: Cannot find module for page: /404
at node_modules/next/dist/export/index.js:493:19

Build error occurred
Error: Export encountered errors on following paths: /404

Expected Behavior

The page rendering should proceed without error.

To Reproduce

Enable concurrentFeatures: true in next.config.js

@saurabhguptarock saurabhguptarock added the bug Issue was opened via the bug report template. label Nov 8, 2021
@saurabhguptarock saurabhguptarock changed the title Error occurred prerendering page "/404" Error occurred prerendering page "/404" when using concurrentFeatures: true Nov 8, 2021
@timneutkens timneutkens added the please add a complete reproduction The issue lacks information for further investigation label Nov 8, 2021
@vitormv
Copy link

vitormv commented Nov 9, 2021

This was already fixed in the canary: https://github.com/vercel/next.js/releases/tag/v12.0.4-canary.0

@huozhi
Copy link
Member

huozhi commented Nov 9, 2021

Thanks @vitormv!
@saurabhguptarock Should be covered in #31059. Can you try it again with next@12.0.4-canary.0. If it still doesn't get fixed please provide a minimal reproduction and reopen the issue. Close the issue for now.

@huozhi huozhi closed this as completed Nov 9, 2021
@balazsorban44
Copy link
Member

This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.

@vercel vercel locked as resolved and limited conversation to collaborators Jan 27, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug Issue was opened via the bug report template. please add a complete reproduction The issue lacks information for further investigation
Projects
None yet
Development

No branches or pull requests

5 participants