Prerender ignores Vite's root: `vite build <dir>` and `createBuilder({ root })` fail from another folder
Los mantenedores suelen responder en 1 día
@aaronanish-t ya está trabajando en esto.
Desde el 4/11/2026.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Error
- Claridad
- Bien especificado
- Estado de actividad
- Estancado
- Stack tecnológico
- bun, react, typescript, vite
- Área
- backend, build-system
Línea de trabajo
Read src/vite/prerender.ts, src/vite/preview-server-plugin/plugin.ts, and src/vite/post-server-build.ts, then reproduce with the linked minimal project by running vite build project from its parent directory. Trace how the resolved Vite root is used for preview startup and output paths. Done means prerender succeeds and all generated files land under project/dist/; linked PR #8826 is already open.
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
When Vite's root is not the working directory, the prerender step after vite build fails. The client and SSR builds succeed.
Prerender resolves paths against process.cwd() instead of the build's resolved root, in three places (@tanstack/start-plugin-core 1.171.55, same code on main):
src/vite/prerender.tsL68-74:vite.preview()gets onlyconfigFile, so the preview config takes itsrootfromprocess.cwd(). The Start plugin then looks forsrcDirectoryunder the working directory, and the preview server fails to start.src/vite/preview-server-plugin/plugin.tsL39-43:getServerOutputDirectory(server.config)returns the relativebuild.outDir(dist/server), andpathToFileURL()resolves it againstprocess.cwd(). The prerender request for/returns 500.src/vite/prerender.tsL29 andsrc/vite/post-server-build.tsL18: the client output directory stays relative.src/prerender.tsL194-195 (path.resolve(outputDir, …)) and the sitemap step then writeindex.html,pages.jsonandsitemap.xmlto<cwd>/dist/client. The build exits 0, so this one is silent.
Vite keeps build.outDir relative in the resolved config and resolves it with path.resolve(config.root, outDir) itself.
Complete minimal reproducer
Reproduction repository: https://github.com/loriensleafs/tanstack-start-prerender-root-repro
The files, all in repro/project/:
package.json
{
"name": "start-prerender-root-repro",
"private": true,
"type": "module",
"scripts": { "build": "vite build" },
"dependencies": {
"@tanstack/react-router": "1.170.46",
"@tanstack/react-start": "1.169.4",
"react": "19.3.1",
"react-dom": "19.3.1"
},
"devDependencies": {
"@vitejs/plugin-react": "6.1.2",
"vite": "8.3.5"
}
}
vite.config.ts
import { tanstackStart } from '@tanstack/react-start/plugin/vite'
import viteReact from '@vitejs/plugin-react'
import { defineConfig } from 'vite'
export default defineConfig({
plugins: [
tanstackStart({
srcDirectory: 'app',
prerender: { enabled: true },
}),
viteReact(),
],
})
build.ts (the programmatic form)
import { createBuilder } from 'vite'
const builder = await createBuilder({ root: import.meta.dirname })
await builder.buildApp()
app/router.tsx
import { createRouter } from '@tanstack/react-router'
import { routeTree } from './routeTree.gen'
export function getRouter() {
return createRouter({ routeTree })
}
app/routes/__root.tsx
import { HeadContent, Outlet, Scripts, createRootRoute } from '@tanstack/react-router'
export const Route = createRootRoute({
head: () => ({ meta: [{ charSet: 'utf-8' }, { title: 'Repro' }] }),
component: () => (
<html>
<head>
<HeadContent />
</head>
<body>
<Outlet />
<Scripts />
</body>
</html>
),
})
app/routes/index.tsx
import { createFileRoute } from '@tanstack/react-router'
export const Route = createFileRoute('/')({
component: () => <h1>Hello from the prerender</h1>,
})
Steps to Reproduce the Bug
-
cd repro/project && bun install -
bun --bun vite build: passes, anddist/client/index.htmlis written. -
rm -rf dist && cd ..(now inrepro/) -
bun --bun project/node_modules/.bin/vite build project: fails after the client and SSR builds:error during build: Error: Failed to start the Vite preview server for prerendering [cause]: Error: Could not resolve entry for router entry: router in /path/to/repro/app -
bun --bun project/build.ts: the same error (createBuilder({ root })).
Each of the following runs starts from repro/:
vite.config.ts change |
Result |
|---|---|
| none | Fails: router in /path/to/repro/app (step 4) |
none, default src/ and no srcDirectory |
Fails: router in /path/to/repro/src |
root: import.meta.dirname |
Preview starts, prerender fails: Failed to fetch /: Internal Server Error, from Cannot find module '/path/to/repro/dist/server/server.js' |
root + absolute environments.ssr.build.outDir (and sitemap.enabled) |
Exit 0, but index.html, pages.json and sitemap.xml go to /path/to/repro/dist/client/, and project/dist/client/ holds only assets/ |
root + absolute build.outDir |
Passes |
nitro() added (nitro 3.0.260903-beta), no root |
Fails: router in /path/to/repro/app |
nitro() added + root: import.meta.dirname |
Passes |
Expected behavior
As a user, I expected vite build project and createBuilder({ root }) to prerender the same as vite build from inside project/, with all output under project/dist/. Instead, the prerender looks for the source and the build output under the working directory, and fails or writes the pages there.
Screenshots or Videos
N/A (build time).
Platform
- Router / Start Version:
@tanstack/react-start1.169.4 (@tanstack/start-plugin-core1.171.55, the latest on npm),@tanstack/react-router1.170.46 - OS: macOS (arm64)
- Browser: N/A (build time)
- Browser Version: N/A
- Bundler: vite (
@vitejs/plugin-react6.1.2, React 19.3.1) - Bundler Version: 8.3.5
- Runtime: Bun 1.4.4 (
bun --bun). Not tried with Node.
Additional context
Workaround. With Nitro, set root: import.meta.dirname in vite.config.ts. Without Nitro, also set an absolute build.outDir:
import { join } from 'node:path'
export default defineConfig({
root: import.meta.dirname,
build: { outDir: join(import.meta.dirname, 'dist') },
// plugins as above
})
Suggested fix. Pass the resolved root to the preview server, and resolve both output directories against it:
// src/vite/prerender.ts
- const outputDir = clientEnv.config.build.outDir
+ const outputDir = path.resolve(clientEnv.config.root, clientEnv.config.build.outDir)
…
return await vite.preview({
configFile: viteConfig.configFile,
+ root: viteConfig.root,
preview: { port: 0, open: false },
})
// src/vite/preview-server-plugin/plugin.ts
- const serverOutputDir = getServerOutputDirectory(server.config)
+ const serverOutputDir = path.resolve(server.config.root, getServerOutputDirectory(server.config))
// src/vite/post-server-build.ts
- return getClientOutputDirectory(builder.config)
+ return path.resolve(builder.config.root, getClientOutputDirectory(builder.config))
I patched these edits into dist/esm of 1.171.55. With them, steps 4 and 5 pass with the config above plus sitemap: { enabled: true, host }, all output lands in project/dist/client/, and nothing is written to repro/. Step 2 still passes, and the Nitro variant passes without root.
Related. #7593 and #8615 forward configLoader in the same vite.preview() call. #8430 moves that call into a worker, and it still passes only configFile. Neither passes root.
Separately, @tanstack/router-generator (src/config.ts, resolveTmpDir) resolves tmpDir against process.cwd(), so an empty .tanstack/tmp folder appears in the working directory. It does not break the build.
This report was drafted with AI assistance. Each run above was made on the versions listed.
- Lenguaje dominante
- TypeScript
- Estrellas
- 15.3k
- Forks
- 1.9k
- Merge medio
- 1 d 5 h
- PR fusionados (30 d)
- 46
Preparar el entorno
Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.
- Sin Dockerfile ni archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de TanStack/router
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
Los mantenedores suelen responder en 1 día
-
Masked navigation drops the first character of the hash each time (__tempLocation hash missing '#')Posiblemente ocupada @hassanabrar202 la tomó hace 8 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
router-generator: lazy-load Prettier (costs ~300–450ms per build even when formatting is off)Posiblemente ocupada @Sheraff la tomó hace 27 días. Abiertopackage: router-generator performance
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
Los mantenedores suelen responder en 1 día
-
router-generator: sibling `physical()` subtrees in a virtual route config generate duplicate identifiersPosiblemente ocupada @Sheraff la tomó hace 27 días. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
Los mantenedores suelen responder en 1 día
-
docs(router): clarify static title fallback in SPA modePosiblemente ocupada @Rohan-Dedhia la tomó hace 17 días. Abierto
Dificultad 1/5 1-3 horas Aptitud para principiantes 62/100
Los mantenedores suelen responder en 1 día
Todos los issues de TanStack/router
Issues similares
-
[BUG]: Shared links drop the configured basePath on GitHub PagesPosiblemente ocupada @anshulchikhale30-p la tomó hoy. Abiertobug
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
StabilityNexus/IdentityTokens-EVM-Frontend#182 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
Add: GTrekkerAbiertocheck:passed streams:add
Dificultad 1/5 Menos de una hora Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 70/100
Koenkk/zigbee-herdsman-converters#13900 ·
Los mantenedores suelen responder en 1 día
-
area: ui Bug Payload OSS
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
payloadcms/payload#19839 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 1/5 Menos de una hora Aptitud para principiantes 88/100
jeanibarz/knowledge-base-mcp-server#1291 ·
Los mantenedores suelen responder en 1 día