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 天 5 小时
- 30 天内合并 PR
- 34
环境准备
- 没有 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 于 54 天前认领。 未关闭1.x
难度 2/5 1-3 小时 新手友好度 78/100
solidjs/solid-vite-plugin#205 · 1 条评论 · 2 个 reaction ·
维护者通常 1 天内回复
-
难度 3/5 半天 新手友好度 55/100
solidjs/solid-vite-plugin#420 ·
维护者通常 1 天内回复
-
难度 5/5 一周以上 新手友好度 25/100
solidjs/solid-vite-plugin#419 ·
维护者通常 1 天内回复
-
难度 4/5 1-2 天 新手友好度 30/100
solidjs/solid-vite-plugin#418 ·
维护者通常 1 天内回复
-
Dev manifest loses lazy CSS when imported before HTTP startup可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 4/5 3-5 天 新手友好度 25/100
solidjs/solid-vite-plugin#414 · 1 条评论 ·
维护者通常 1 天内回复
查看 solidjs/solid-vite-plugin 的全部 Issue
相似的 Issue
-
area:ui effort:S enhancement priority:P2
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 74/100
QuantumNous/new-api#7839 ·
维护者通常 1 天内回复
-
good first issue maintenance
难度 2/5 1-3 小时 新手友好度 62/100
dark-princezz/stellar-hooks#1010 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
interledger/rhyza#352 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
维护者通常 1 天内回复