Solid Start rc.11 depends on a published Start Server Core without the request-scope export

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

维护者通常 1 天内回复

@brenelz 已经在做这个了。

开始于 2026年11月22日。

  • #8973 来自 @brenelz —— 未关闭

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
58/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
bun, node.js, typescript, vite

调研方向

Start with the createSolidStartHandler.js import and the @tanstack/[email protected] package exports; the issue links to both published files. Reproduce the resolution error using the provided Node command, then check the existing export change in #8937 and how the next RC selects its dependency. Done when the declared published dependency resolves @tanstack/start-server-core/request-scope and the SSR build succeeds.

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

描述

Which project does this relate to?

Start

Describe the bug

@tanstack/[email protected] imports @tanstack/start-server-core/request-scope in createSolidStartHandler.js. Its pinned dependency, @tanstack/[email protected], omits ./request-scope from exports. This blocks the SSR build with Vite and the Cloudflare plugin.

Complete minimal reproducer

The released packages reproduce the resolution error in an empty directory. The Solid Start import and the Start Server Core manifest are also available directly.

Steps to Reproduce the Bug
mkdir solid-start-rc11-repro
cd solid-start-rc11-repro
bun add [email protected] @solidjs/[email protected] @tanstack/[email protected]
node --experimental-import-meta-resolve --input-type=module - <<'JS'
const from = import.meta.resolve("@tanstack/solid-start/package.json")
console.log(import.meta.resolve("@tanstack/start-server-core/request-scope", from))
JS

Node reports ERR_PACKAGE_PATH_NOT_EXPORTED for ./request-scope.

Expected behavior

The published Solid Start RC resolves its server entry with the dependency versions it declares.

Platform
  • Solid Start 2.0.0-rc.11, Start Server Core 1.169.45, Solid 2.0.1
  • Node 24.22.2, Bun 1.4.4, Vite 8.3.7, macOS arm64
Additional context

#8937 already adds the export on solid-router-v2-pre. Could the next RC depend on a published Start Server Core build that includes it? As a local workaround, exposing ./dist/esm/internal-request-response.js at that subpath in 1.169.45 allowed the SSR build and Workerd route smoke tests to pass.

AI-assisted report with the reproducer run locally.

主要语言
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 摘要。