Prerendering fails if file-based routing is disabled, but there are .vue files in pages directory about nuxt HOT 9 CLOSED

I'd be happy to take a look at this

from nuxt.

@danielroe Thanks for your patience. I've been helping my wife with morning sickness (we're having another kid!!!).

Anyway, regarding the prerenderRoutes function, I played around with it to learn how prerendering works and see that it is only additive to what the prerenderer generates. Given nitro is preconfigured to generate all of the routes in the pages directory, are you suggesting that we remove this logic from the module and expose the routes to crawl using the plugin?

(pls correct me if my understanding is wrong)

from nuxt.

Start a new pull request in StackBlitz Codeflow.

• nuxt-starter-sgbtc2 (Open reproduction)

from nuxt.

It seems nitro is being handed the wrong route options when prerendering here

I'm debugging further

from nuxt.

The prerender config is set by this line which sets it to a set of pages from created only from pages within the /pages directory.

The custom router.options.ts seems only imported by the runtime code generated by this template.

I see now that the pages module doesn't have the final routing config in memory when creating the prerendering config.

I see a few ways to tackle this. Let me know if there are others.

1. Import the router.options.ts file (and any other files) in the pages module to discover what the final routing config resolves to.
   • Is there precedent for something similar elsewhere in nuxt? I haven't found anything yet, but I'll keep looking.
2. Change the way prerendering works to introspect the running site to discover what routes exist.
   • Based on what I know about nitro and nuxt thus far, this seems like it would require a change to nitro and the generated app for prerendering. I could be wrong though.

@danielroe any thoughts?

from nuxt.

I think we should use a Nuxt plugin that is guarded by import.meta.prerender so it does not add anything to the final build, and which only executes once, passing all paths to the prerenderRoutes composable.

(this would only be if ssr: true)

from nuxt.

Just to make sure we are talking about the same piece of code, you're referring to this composable correct?

Also, I'll be happy to take this on if you want to assign it to me.

from nuxt.

Yes. And go for it ❤️

from nuxt.

Yes, that’s what I’m suggesting…

from nuxt.