Is Cloudflare Pages support of Tanstack Start silently being removed?

[nicu-chiciuc]

For the past few weeks I've been trying to piece together what's happening with Cloudflare Pages support.

I would usually let Codex set everything up using official docs, but it seems that official docs are confusing:
https://tanstack.com/start/latest/docs/framework/solid/guide/spa-mode

# Catch all other 404 requests and rewrite them to the SPA shell
/* /_shell.html 200

This _redirects file, that seems important, breaks Cloudflare Pages support.

It seems there was active docs for cloudflare pages which where replaced with Cloudflare Workers:
#4898

I've found other prs/issues/reddit threads about Cloudflare Pages issues. And it's not about advanced features, it's about setting up a starter stack.

It's not clear what the incentives are, but for the past 2 weeks I felt like I'm doing something wrong and I'm actively forced to go from cf pages to cf workers.

But this seems to go against the Tanstack Start goal of being client-side first.

[nktnet1]

I ran into a similar issue with deployment - the fix in my case was changing _shell.html to index.html in my vite.config.ts, E.g. with:

export default defineConfig({

  // ...

  plugins: [

    // ...

    tanstackStart({
      spa: {
        enabled: true,
        prerender: {
          outputPath: "index.html", // <---------- This line
          enabled: true,
          crawlLinks: true,
        },
      },
    }),
    
    // ...

  ],
  
  // ...

}