How to deal with prerender - error on bigger projects

[dohomi]

Hi Guys,

I run in a pretty big project into a https://github.com/vercel/next.js/blob/master/errors/prerender-error.md due to broken/misspelled links deep nested in my page tree (headless CMS).

Due to the error the build process (SSG) never succeeds. Is there a way to print out the broken links and on which they happen? Currently its quite difficult to keep track on broken links.

Is there (probably out of NextJS) a good spider/crawler which I could run over an entire site and test if all links are still working? Any suggestions are welcome! Thanks

[dohomi]

I am fighting with this error message in particular:

  
Error occurred prerendering page "/". Read more: https://err.sh/next.js/prerender-error  
Error: The provided export path '/' doesn't match the '/[...index]' page.

Is there a possibility to get more information about this kind of error? Or to still finalize the build and not stopping it?

[Timer]

The /[...index] pages does not match /, which is causing this error (re: the error message).

[dohomi]

But I will definitely try to prevent this falsy entry code wise, I just wanted to share that it might be helpful if the error would be more specific on which slug it actually is being thrown

[dohomi]

Maybe I have some code from the optional catch all still inside of my codebase. As far I could see you are publishing it with the upcoming version. Thanks for your input I will investigate. Maybe Ill try the latest canary and rewrite [...index] to [[...index]]

[Timer]

@dohomi the error is very specific that you are trying to render "/" (that is the slug / path) on the page /[...index] which is not valid. Could you please elaborate what you mean?

The only way to get / to work without being a real page is optional catch all routes.

[dohomi]

Yes I meant the optional catch-all routes, I'll give it a try. Thanks for your input I'll know now how to proceed