SPA initial route stays pending with `basepath` under Tauri’s (or any other) custom protocol
I maintainer di solito rispondono entro 1 giorno
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 45/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- react, typescript, vite
- Ambito
- frontend
Direzione di ricerca
Start in packages/router-core/src/router.ts around the origin handling near line 131 and the URL classification/buildLocation path near line 2596. Reproduce with the linked minimal repo, then compare buildLocation() output under http:// versus tauri:// with a non-root basepath, focusing on whether publicHref becomes absolute and external flips true. Done means the initial route loads under the custom protocol with the basepath preserved, with a regression test covering custom-protocol origins.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Which project does this relate to?
Router
Describe the bug
A TanStack Start SPA works when served over HTTP, but its initial index route remains pending when the same build is loaded through Tauri’s tauri:// protocol with a non-root base path.
JavaScript executes, React mounts, and state updates work. The index route has no loader, beforeLoad, or data fetching. However, the initial router.load() is never called under Tauri.
Removing the base path fixes startup. Normalizing buildLocation() output to a relative publicHref and setting external: false also fixes it while preserving the base path.
I think it's worth fixing because not only tauri is affected, but any custom webview-like solution with non-http loader (eg. electron uses file://)
Complete minimal reproducer
https://github.com/kpostekk/tanstack-router-protocol-basepath-issue-20261115
Steps to Reproduce the Bug
-
Build the SPA with the configuration above.
-
Serve the output at http://localhost:7644/app-x/ - the index route renders. This can be modified in tauri.conf.json
-
Load the same output through Tauri at tauri://localhost:7644/app-x/ - the root shell renders, but the index route remains pending.
-
Remove Vite base and router basepath, rebuild, and load at tauri://localhost:7644/: the index route renders.
Expected behavior
The initial route should load under the custom protocol with a base path, as it does over HTTP and under the custom protocol without a base path.
Actual behavior
The router remains in this state:
{
"status": "idle",
"pathname": "/",
"matches": [
{ "routeId": "__root__", "status": "success" },
{ "routeId": "/", "status": "pending" }
]
}
Instrumenting router.load() shows:
-
HTTP: called with { sync: true }; both matches become successful.
-
Tauri: no initial call.
-
Manual router.invalidate(): the index route renders successfully.
URL comparison
I compared router.latestLocation with:
router.buildLocation({
to: '/',
search: true,
hash: true,
})
const router = useRouter()
useEffect(() => {
const current = router.latestLocation
const generated = router.buildLocation({
to: '/',
search: true,
hash: true,
})
console.log('[URL comparison]', {
browser: window.location.href,
basepath: router.options.basepath,
origin: router.options.origin,
currentHref: current.href,
currentPublicHref: current.publicHref,
generatedHref: generated.href,
generatedPublicHref: generated.publicHref,
})
}, [router])
Results:
| Value | HTTP | Tauri |
|---|---|---|
| Browser URL | http://localhost:7644/app-x/ |
tauri://localhost:7644/app-x/ |
router.options.basepath |
"app-x" |
"app-x" |
Current href |
/ |
/ |
Current publicHref |
/app-x/ |
/app-x/ |
Generated href |
/app-x/ |
/app-x/ |
Generated publicHref |
/app-x/ |
tauri://localhost:7644/app-x/ |
In the Tauri webview, both location.origin and new URL(location.href).origin return tauri://localhost:7644, rather than "null".
Explicitly setting the router’s origin to window.location.origin did not resolve the issue.
Suspected source
These locations look relevant to the origin handling and generated URL classification:
My suspicion is that the rewrite path used by basepath produces an absolute URL or classifies the location as external under the custom protocol, affecting startup. I have not confirmed the exact failing condition.
Working workaround
Wrapping buildLocation() immediately after router creation fixes startup:
if (
typeof window !== 'undefined' &&
window.location.protocol === 'tauri:'
) {
const buildLocation = router.buildLocation.bind(router)
router.buildLocation = ((...args) => {
const location = buildLocation(...args)
const url = new URL(location.publicHref, window.location.href)
if (
url.protocol === window.location.protocol &&
url.host === window.location.host
) {
return {
...location,
publicHref: `${url.pathname}${url.search}${url.hash}`,
external: false,
}
}
return location
}) as typeof router.buildLocation
}
This changes both publicHref and external; I have not isolated which change is necessary.
Screenshots or Videos
No response
Platform
- Router / Start Version: 1.169.5
- OS: Linux Fedora 45
- Browser: Webkit2gtk-4.1
- Browser Version: 605.1.15
- Bundler: vite
- Bundler Version: 8.3.8
Additional context
- The route chunk imports successfully.
- React state updates work in the root shell.
- Removing the outer
ClientOnlywrapper does not help. - Removing React Compiler does not help.
- The issue occurs with a trivial index component and no route loaders.
- Lingua principale
- TypeScript
- Stelle
- 15.3k
- Fork
- 1.9k
- Merge medio
- 1g 5h
- PR unite (30g)
- 46
Preparare l'ambiente
Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di TanStack/router
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
I maintainer di solito rispondono entro 1 giorno
-
Masked navigation drops the first character of the hash each time (__tempLocation hash missing '#')Forse già presa @hassanabrar202 l’ha presa 8 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
I maintainer di solito rispondono entro 1 giorno
-
router-generator: lazy-load Prettier (costs ~300–450ms per build even when formatting is off)Forse già presa @Sheraff l’ha presa 27 giorni fa. Apertapackage: router-generator performance
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
I maintainer di solito rispondono entro 1 giorno
-
router-generator: sibling `physical()` subtrees in a virtual route config generate duplicate identifiersForse già presa @Sheraff l’ha presa 27 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
I maintainer di solito rispondono entro 1 giorno
-
docs(router): clarify static title fallback in SPA modeForse già presa @Rohan-Dedhia l’ha presa 17 giorni fa. Aperta
Difficoltà 1/5 1-3 ore Idoneità per principianti 62/100
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di TanStack/router
Issue simili
-
[BUG]: Shared links drop the configured basePath on GitHub PagesForse già presa @anshulchikhale30-p l’ha presa oggi. Apertabug
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
StabilityNexus/IdentityTokens-EVM-Frontend#182 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Add: GTrekkerApertacheck:passed streams:add
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 72/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
Koenkk/zigbee-herdsman-converters#13900 ·
I maintainer di solito rispondono entro 1 giorno
-
area: ui Bug Payload OSS
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
payloadcms/payload#19839 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
jeanibarz/knowledge-base-mcp-server#1291 ·
I maintainer di solito rispondono entro 1 giorno