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

Abierto
#8,964 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

@brenelz ya está trabajando en esto.

Desde el 22/11/2026.

  • #8973 de @brenelz — abierto

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
58/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
bun, node.js, typescript, vite

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
TypeScript
Estrellas
15.3k
Forks
1.9k
Merge medio
1 d 5 h
PR fusionados (30 d)
46

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de TanStack/router

Todos los issues de TanStack/router

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.