SPA initial route stays pending with `basepath` under Tauri’s (or any other) custom protocol

未关闭
#8,936 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

@hassanabrar202 已经在做这个了。

开始于 2026年11月15日。

  • #8938 来自 @hassanabrar202 —— 未关闭

评估

难度
4/5
预计耗时
3-5 天
新手友好度
45/100
Issue 类型
缺陷
描述清晰度
基本清楚
活跃度
活跃
技术栈
react, typescript, vite
领域
frontend

调研方向

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.

由索引模型根据 Issue 内容生成。

描述

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
  1. Build the SPA with the configuration above.

  2. Serve the output at http://localhost:7644/app-x/ - the index route renders. This can be modified in tauri.conf.json

  3. Load the same output through Tauri at tauri://localhost:7644/app-x/ - the root shell renders, but the index route remains pending.

  4. 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 ClientOnly wrapper does not help.
  • Removing React Compiler does not help.
  • The issue occurs with a trivial index component and no route loaders.
主要语言
TypeScript
星标
15.3k
派生
1.9k
平均合并
1 天 5 小时
30 天内合并 PR
46

环境准备

在 Codespaces 中打开

在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

TanStack/router 的其他 Issue

查看 TanStack/router 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。