Route CSS removed on first client-side navigation and never restored (client manifest is pruned to SSR'd matches)
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
- #8225 di @breken-ai — chiusa senza merge
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 72/100
- Tipo di issue
- Bug
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- react, typescript
Direzione di ricerca
Inizia tracciando la disidratazione del manifest in router-core/dist/esm/ssr/ssr-server.js, l’assegnazione del client in load-client.js e la ricerca/rimozione del CSS in react-router/dist/esm/headContentUtils.js. Riproduci una build di produzione caricando la route SSR e navigando lato client verso la route del componente condiviso; il lavoro è completato quando i link CSS condivisi rimangono disponibili o vengono ripristinati dopo la navigazione senza disabilitare lo splitting del CSS.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Summary
On the first client-side navigation away from the server-rendered route, HeadContent removes that route's manifest CSS <link> elements. If the incoming route reuses the same chunk — a component rendered by both routes — nothing re-declares those stylesheets and nothing re-injects them, so the page keeps its class names and loses every rule.
The result looks like a stylesheet that failed to load, but DevTools shows every .css at 200. They loaded, and then their <link> elements were deleted.
Versions
@tanstack/react-start 1.168.49 (latest)
@tanstack/react-router 1.170.32 (latest)
@tanstack/router-core 1.171.27 (latest)
vite 7.3.6 · react 18.3.1 · SSR via Nitro
Reproduction
- A component
<Dashboard />with a CSS-module import, rendered by two routes:/(index)/pool(a layout route, parent of/pool/$id)
- Build for production and load
/directly, so it is server-rendered. - Client-side navigate to
/pool/$id.
Dashboard's stylesheet is removed from <head> and never restored.
It does not reproduce if you arrive at / by client-side navigation from some other route — then the CSS came from Vite's runtime injection, which the router doesn't own and therefore doesn't remove. That asymmetry is what makes it look intermittent in the wild.
What's happening
getStartManifest()returns assets for all routes.serverSsr.dehydrate()prunes to only the matched routes before sending to the client —router-core/dist/esm/ssr/ssr-server.js:301, viagetPreparedMatchedManifestRoutes→prepareMatchedManifestRoutes(:145-161, which iteratesmatchesonly).- The client assigns that pruned object as the whole manifest —
load-client.js:1075:router.ssr = { manifest: dehydratedRouter.manifest }; HeadContentlooks upmanifest.routes[match.routeId]?.css(react-router/dist/esm/headContentUtils.js:65). For any route not in the original SSR match set this isundefined, so no CSS tags are produced.- React unmounts the outgoing route's
<link>elements — correctly, they're its own keyed children. - Vite does not re-inject, because the chunk is already in its module cache.
Observed client-side after loading /:
routes in client manifest: 2 -> __root__, /
"/" css: TooltipButton, GalleryIcon, FocusReveal, BookmarkDashboard
"/pool" css: (NONE)
The server-side manifest has all 34 routes, and /pool there correctly lists all four stylesheets. Only the client's copy is missing them.
MutationObserver on <head> across the navigation, bracketed by the title swap:
12947ms add LINK stylesheet pool-PDzBNjqJ.css <- Vite, for the newly loaded chunk
13464ms REMOVE TITLE
13464ms REMOVE LINK modulepreload ...16 entries...
13464ms REMOVE LINK stylesheet TooltipButton-Dla7QkuC.css
13464ms REMOVE LINK stylesheet GalleryIcon-BwNEuhX0.css
13464ms REMOVE LINK stylesheet FocusReveal-CakzEOUS.css
13464ms REMOVE LINK stylesheet BookmarkDashboard-5xTt8aTr.css
13464ms add TITLE
All three matches are success at that moment (__root__, /pool, /pool/$idSlug), so _getAssetMatches truncation is not involved.
Elements keep their hashed class names (_searchContainer_15j3j_55); the rules are simply gone — padding: 20px 20px 15px → 0px, display: flex → block.
Expected
Either:
- the dehydrated manifest carries assets for all routes (or is extended as routes load), so
HeadContentcan re-declare a stylesheet a newly matched route needs; or HeadContentdoes not remove a stylesheet<link>it cannot guarantee re-adding.
The current combination — prune the client manifest to the SSR'd matches, then remove head assets by route on navigation — means any chunk shared between an SSR'd route and a later-visited route loses its CSS.
Workaround
build.cssCodeSplit: false. One stylesheet, which the manifest attaches to __root__ — always matched, never unmounted, so there is nothing to tear down. Costs ~23 KB gzipped on first load for us.
Note
Filed from a production incident. Happy to put together a minimal standalone reproduction if that would help — the shape above is the whole of it, and the internal trace is included so it can be verified by inspection in the meantime.
- Lingua principale
- TypeScript
- Stelle
- 15.3k
- Fork
- 1.9k
- Merge medio
- 1g 5h
- PR unite (30g)
- 46
Preparare l'ambiente
Avvia il container di sviluppo del progetto nel browser, con il tuo account GitHub.
- Nessun Dockerfile né file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di TanStack/router
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
I maintainer di solito rispondono entro 1 giorno
-
Masked navigation drops the first character of the hash each time (__tempLocation hash missing '#')Forse già presa @hassanabrar202 l’ha presa 8 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
I maintainer di solito rispondono entro 1 giorno
-
router-generator: lazy-load Prettier (costs ~300–450ms per build even when formatting is off)Forse già presa @Sheraff l’ha presa 27 giorni fa. Apertapackage: router-generator performance
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
I maintainer di solito rispondono entro 1 giorno
-
router-generator: sibling `physical()` subtrees in a virtual route config generate duplicate identifiersForse già presa @Sheraff l’ha presa 27 giorni fa. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
I maintainer di solito rispondono entro 1 giorno
-
docs(router): clarify static title fallback in SPA modeForse già presa @Rohan-Dedhia l’ha presa 17 giorni fa. Aperta
Difficoltà 1/5 1-3 ore Idoneità per principianti 62/100
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di TanStack/router
Issue simili
-
[BUG]: Shared links drop the configured basePath on GitHub PagesForse già presa @anshulchikhale30-p l’ha presa oggi. Apertabug
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
StabilityNexus/IdentityTokens-EVM-Frontend#182 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Add: GTrekkerApertacheck:passed streams:add
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 72/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
Koenkk/zigbee-herdsman-converters#13900 ·
I maintainer di solito rispondono entro 1 giorno
-
area: ui Bug Payload OSS
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
payloadcms/payload#19839 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
jeanibarz/knowledge-base-mcp-server#1291 ·
I maintainer di solito rispondono entro 1 giorno