Dev manifest bridge keeps stale CSS after an edit
維護者通常 1 天內回覆
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 34/100
- Issue 類型
- 缺陷
- 描述清晰度
- 基本清楚
- 活躍度
- 活躍
- 技術堆疊
- typescript
- 領域
- build-system, frontend
研究方向
Start with the HTTP bridge resolver generated by virtual:solid-manifest and find where it caches CSS for the isolated SSR runner. Reproduce with a lazy component importing page.css: fetch, edit the rule from 18px to 36px, then fetch again without restarting. Done when the second response contains the new rule and no stale one, and in-flight requests cannot restore old CSS.
由索引模型根據 Issue 內容生成。
描述
The HTTP bridge resolver generated by virtual:solid-manifest caches CSS in the isolated SSR runner. After a CSS edit, the resolver in the Vite process clears its cache, but the bridge consumer keeps the old result.
I reproduced this with a real Nitro dev worker using @solidjs/[email protected], [email protected], @solidjs/[email protected], [email protected], and [email protected]. The same cache implementation is still present in 3.0.0-next.50.
Steps:
- Render a lazy component that imports
page.css, with.bridge_probe { font-size: 18px; }. - Fetch the page and confirm the raw SSR response contains that rule.
- Change the rule to
font-size: 36pxand wait for Vite to process the file change. - Fetch the page again without restarting the dev server.
The second response still contains 18px and does not contain 36px. Both responses are HTTP 200 and contain the page content. This reproduces even when the separate early-startup bridge URL problem is avoided by delaying manifest loading until the server is listening.
The browser eventually replaces the old styles during hydration. That leaves a visible layout change on a document reload.
The bridge cache needs invalidation when its styles change. Cached lookups must still return synchronously: returning a new Promise on every lookup prevents suspended lazy SSR renders from converging. Pending requests also need to be accounted for so a response started before invalidation cannot restore stale CSS.
- 主要語言
- TypeScript
- 星號
- 522
- 分支
- 73
- 平均合併
- 1 天 4 小時
- 30 天內合併 PR
- 35
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 沒有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
solidjs/solid-vite-plugin 的其他 Issue
-
Test environment detection doesn't consider Vitest workspaces可能已有人在做 @carloitaben 於 55 天前認領。 未關閉1.x
難度 2/5 1-3 小時 新手友好度 78/100
solidjs/solid-vite-plugin#205 · 1 則留言 · 2 個 reaction ·
維護者通常 1 天內回覆
-
Dev: a stylesheet shared by the entry and a lazy component moves after the lazy component's styles未關閉
難度 3/5 半天 新手友好度 62/100
solidjs/solid-vite-plugin#425 ·
維護者通常 1 天內回覆
-
[3.0.0-next.50 / next] SSR build: the $$moduleUrl export added to a Worker main module stops workerd from starting可能已有人在做 關聯的 PR 仍在進行中或已合併。 未關閉
難度 3/5 半天 新手友好度 55/100
solidjs/solid-vite-plugin#420 ·
維護者通常 1 天內回覆
-
難度 5/5 一週以上 新手友好度 25/100
solidjs/solid-vite-plugin#419 ·
維護者通常 1 天內回覆
-
start.node: node.js imports node:http before start.instrument runs, so HTTP instrumentation misses the server可能已有人在做 關聯的 PR 仍在進行中或已合併。 未關閉
難度 4/5 1-2 天 新手友好度 30/100
solidjs/solid-vite-plugin#418 ·
維護者通常 1 天內回覆
查看 solidjs/solid-vite-plugin 的全部 Issue
相似的 Issue
-
`cf complete zsh >> .zshrc` fails on vanilla zsh可能重新可做 關聯的 PR 已關閉且未合併。 未關閉
難度 2/5 1-3 小時 新手友好度 75/100
cloudflare/cf#340 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
-
難度 2/5 1 小時以內 新手友好度 75/100
StoDevX/AAO-React-Native#8785 ·
維護者通常 1 天內回覆
-
難度 1/5 1 小時以內 新手友好度 75/100
-
bnv-manager-v2: accept_invite creates the Mailcow domain admin before the commit可能已有人在做 @myOmikron 今天認領。 未關閉bug ready-for-agent
難度 2/5 1-3 小時 新手友好度 82/100