autoCodeSplitting: imported component used as both component and pendingComponent is left undefined (ReferenceError)

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

Los mantenedores suelen responder en 1 día

@Sheraff ya está trabajando en esto.

Desde el 25/10/2026.

  • #8817 de @Sheraff — abierto
  • #8939 de @EnesKartal — abierto

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
67/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
typescript, vite
Área
build-system

Línea de trabajo

Start in the router plugin’s auto code splitting transform, which handles route component imports; the issue does not name a source file or test. Reproduce with the examples/react/start-bare route and inspect the built server and client router chunks for the missing Page binding. Done when the imported component remains correctly bound when used as both component and pendingComponent, and the route runs without a ReferenceError.

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

With autoCodeSplitting: true, a component that is imported from another module and used as both component and pendingComponent ends up as a free identifier in the built router chunk.

component becomes lazyRouteComponent($$splitComponentImporter, "component"), pendingComponent: Page stays in the main chunk, and the import { Page } is removed. vite build exits 0, but the chunk throws when it is evaluated (server request, or Start prerender):

ReferenceError: Page is not defined
    at file:///.../dist/server/assets/router-DsEmb4my.js:40:20
    at ModuleJob.run (node:internal/modules/esm/module_job:569:25)
    at async node:internal/modules/esm/loader:650:26
    at async Promise.all (index 0)
    at async loadEntries (file:///.../dist/server/server.js:6766:52)

The client chunk has the same pendingComponent:Page with no binding.

Not affected: a component declared in the route file and used for both keys (it goes to a ?tsr-shared=1 module), and a separate pending component.

// src/routes/about.tsx
import { createFileRoute } from '@tanstack/react-router'
import { Page } from '~/components/Page'

export const Route = createFileRoute('/about')({
  loader: () => new Promise((r) => setTimeout(r, 500)),
  component: Page,
  pendingComponent: Page,
})

Built server chunk:

var Route = createFileRoute("/about")({
	loader: () => new Promise((r) => setTimeout(r, 500)),
	component: lazyRouteComponent($$splitComponentImporter, "component"),
	pendingComponent: Page
});

Workaround: codeSplitGroupings: [['component', 'pendingComponent']] on the route.

Complete minimal reproducer

https://github.com/cpeaustriajc/tanstack-router-shared-pending-component-repro

Steps to Reproduce the Bug

The repo is examples/react/start-bare with src/routes/about.tsx changed and src/components/Page.tsx added.

  1. pnpm install
  2. pnpm vite build
  3. grep -n pendingComponent dist/server/assets/router-*.js shows pendingComponent: Page, and the chunk has no import or declaration of Page.
  4. pnpm start and open /about: ReferenceError: Page is not defined.

Control: change to pendingComponent: () => <p>Loading</p>. The build output has no free identifier and /about renders.

Expected behavior

The import stays in the main chunk while pendingComponent (not split) still references it, or the binding is shared the same way as a component declared in the route file.

Screenshots or Videos

No response

Platform
  • Router / Start Version: @tanstack/react-router 1.170.46, @tanstack/react-start 1.169.5, @tanstack/router-plugin 1.169.0, @tanstack/start-plugin-core 1.171.56 (also seen on router-plugin 1.168.48)
  • OS: macOS
  • Browser: n/a (fails on the server)
  • Browser Version: n/a
  • Bundler: vite
  • Bundler Version: 8.3.6
  • Node: 26.12.1
Additional context

This issue was written with an AI assistant (Claude) and checked by running the reproducer from a fresh clone.

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.