Deploy a static Tanstack Start SPA to 2 environments, one with basePath and one without?

[nktnet1]

I would like to deploy an application to:

1. Cloudflare Workers (root URL, no base path)
2. GitHub Pages (has base path /repo-name)

Without needing to drastically change the code and structure - e.g. by simply building with an environment variable such as PUBLIC_DOCS_BASE_PATH.

This doesn't seem possible yet based on what @SeanCassiere stated here:

Once you've changed the apiBase to /path/api, you need to change and update your API route files to match the new pathing.

I have already set the base in vite.config.ts as well as the basepath in src/router.tsx under createTanstackRouter as mentioned in #4888.

My previous version of the site, built with NextJS, was easily deployed to both environments with a simple basePath configuration in next.config.ts:

• https://github.com/nktnet1/webview-kiosk/tree/971213a4c7940614757c46ddcae6f1671eafd961/docs

---

For further context, my application is:

• https://github.com/nktnet1/webview-kiosk/tree/311fbcde6f7b076077e9ce6a344bb00392529a3c/docs

I've deployed it to:

• https://webviewkiosk.nktnet.uk/ (Cloudflare Worker, static SPA)
• https://nktnet1.github.io/webview-kiosk/ (GitHub Pages)

You can see that

1. orama search from fumadocs is broken (utilises /api)

2. navigation is broken (but works when refreshing the error page after navigating)

   • UPDATE: The __tsr/* routes do not respect the configured base path as reported here: build issue: __tsr n ot taking basepath fuma-nama/fumadocs#3123, and tracked in issue staticFunctionMiddleware does not respect basePath configuration #6152

[nktnet1]

From above,

1. Fumadocs Orama Search API is resolved by Search does not work correctlly on custom basePath fuma-nama/fumadocs#899 (comment)

2. Can be resolved by manually patching staticMiddlewareFunction to account for the base path, as demonstrated in fix(docs): manually patch staticMiddlewareFunction for base path nktnet1/webview-kiosk#251.

The second point is a workaround - the resolution is probably to wait until #6152 is fixed (PR: #5970).