Hybrid rendering doesn't generate spa fallback html

[a1mersnow]

Environment

• Operating System: Darwin
• Node Version: v16.20.1
• Nuxt Version: 3.6.5
• Nitro Version: 2.5.2
• Package Manager: pnpm@8.7.4
• Builder: vite
• User Config: nitro, app, ui, devtools, typescript, vue, modules, content, colorMode, vite
• Runtime Modules: @nuxt/content@2.7.2, @nuxthq/ui@2.7.0-28233674.a2970cb
• Build Modules: -

Reproduction

https://stackblitz.com/edit/github-h3ry36?file=nuxt.config.ts

Describe the bug

Got this config:

export default defineNuxtConfig({
  nitro: {
    routeRules: {
      '/**': { prerender: true },
      '/spa': { ssr: false },
    },
    prerender: {
      crawlLinks: true,
      routes: ['/', ],
    },
  },
})

After `pnpm build`, there are no fallback html generated for `spa` page.

If this isn't a bug, how to generate the fallback htmls like nuxt generate?

Additional context

No response

Logs

No response

[stackblitz]

Start a new pull request in StackBlitz Codeflow.

• github-h3ry36 (Open reproduction)

[jf908]

I was having a similar problem but I think I found the solution in the docs.

The spa fallback page is called 200.html.

I turned prerendering off by default via routeRules but this meant that 200.html wasn't being generated. I solved this by adding it to my route rules:

export default defineNuxtConfig({
  routeRules: {
    '/200.html': { prerender: true },
    '/**': { prerender: false },
  },
});

Then I configured my back-end to use 200.html as the fallback page and everything worked.

[a1mersnow]

@jf908 It works!

However, I didn't turn prerendering off by default, but I still need to declare /200.html to make it work:

nitro: {
  routeRules: {
    '/200.html': { prerender: true },
    '/**': { prerender: true },
    '/mine/**': { ssr: false },
    '/shop/**': { ssr: false },
  },
  prerender: {
    crawlLinks: true,
    routes: ['/'],
  },
},

Without your solution, I worked around it previously by using nuxt generate && rm -rf /mine/**/*.html /shop/**/*.html because it will generate 200.html and 404.html(Although I don't known how to use 404.html with nginx. I will appreciate if you can tell me how.).

With your solution, I can get back to the normal nuxt build~

However, I think this should be explicitly documented in docs. @danielroe

[danielroe]

Yes, it would make sense to make sure we explain about 200.html and 404.html and how to generate them.

[zoellner]

Depending on the preset (I am using aws-lambda) it seems that the configuration needs to be slightly different from what is reported here.

What works for me is

export default defineNuxtConfig({
  nitro: {
    prerender: {
      routes: ['/200/index.html'],
    },
    routeRules: {
      '/200/index.html': { ssr: false },
    }
  }
});