Solid Start rc.11 depends on a published Start Server Core without the request-scope export
维护者通常 1 天内回复
评估
- 难度
- 2/5
- 预计耗时
- 1-3 小时
- 新手友好度
- 58/100
- Issue 类型
- 缺陷
- 描述清晰度
- 描述清楚
- 活跃度
- 活跃
- 技术栈
- bun, node.js, typescript, vite
- 领域
- backend, build-system
调研方向
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 Core1.169.45, Solid2.0.1 - Node
24.22.2, Bun1.4.4, Vite8.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
环境准备
在浏览器里用你自己的 GitHub 账号启动这个项目的开发容器。
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
TanStack/router 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 85/100
维护者通常 1 天内回复
-
Masked navigation drops the first character of the hash each time (__tempLocation hash missing '#')可能已有人在做 @hassanabrar202 于 8 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 72/100
维护者通常 1 天内回复
-
router-generator: lazy-load Prettier (costs ~300–450ms per build even when formatting is off)可能已有人在做 @Sheraff 于 27 天前认领。 未关闭package: router-generator performance
难度 2/5 1-3 小时 新手友好度 85/100
维护者通常 1 天内回复
-
router-generator: sibling `physical()` subtrees in a virtual route config generate duplicate identifiers可能已有人在做 @Sheraff 于 27 天前认领。 未关闭
难度 2/5 1-3 小时 新手友好度 76/100
维护者通常 1 天内回复
-
docs(router): clarify static title fallback in SPA mode可能已有人在做 @Rohan-Dedhia 于 17 天前认领。 未关闭
难度 1/5 1-3 小时 新手友好度 62/100
维护者通常 1 天内回复
相似的 Issue
-
[BUG]: Shared links drop the configured basePath on GitHub Pages可能已有人在做 @anshulchikhale30-p 今天认领。 未关闭bug
难度 1/5 1 小时以内 新手友好度 88/100
StabilityNexus/IdentityTokens-EVM-Frontend#182 · 1 条评论 ·
维护者通常 1 天内回复
-
Add: GTrekker未关闭check:passed streams:add
难度 1/5 1 小时以内 新手友好度 72/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
Koenkk/zigbee-herdsman-converters#13900 ·
维护者通常 1 天内回复
-
area: ui Bug Payload OSS
难度 1/5 1 小时以内 新手友好度 88/100
payloadcms/payload#19839 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 88/100
jeanibarz/knowledge-base-mcp-server#1291 ·
维护者通常 1 天内回复