fix(loader-client,loader-server): the watchers throttle on the first event instead of debouncing
維護者通常 1 天內回覆
還沒有人認領這個 Issue。
評估
- 難度
- 3/5
- 預估耗時
- 1-2 天
- 新手友好度
- 70/100
- Issue 類型
- 缺陷
- 描述清晰度
- 描述清楚
- 活躍度
- 活躍
- 技術堆疊
- bun, typescript
- 領域
- devtools
研究方向
Read apps/client/src/watch.ts and apps/server/src/watch.ts at the cited lines, then compare their event handling with the debounce behavior documented in docs/docs/client.mdx and docs/docs/server.mdx. Add or update watcher tests if the project has them, and verify that a burst triggers one reload or restart after its last event, with each watched folder handled independently.
由索引模型根據 Issue 內容生成。
描述
Which app is this bug report for?
other
Issue description
Applies to client and server.
Both watchers act on the first fs event and ignore the following ones for 100 ms (client watch.ts#L29-L45, server watch.ts#L4-L11).
- A build that writes its files over more than 100 ms triggers a reload or restart in the middle of the build: the page can fetch the manifest of a half-written build, and the changes inside the window are dropped.
- The client's two watchers (client dir and
--watch-server-dir) share onelastCall, so a server change less than 100 ms after a client change is lost. - The docs describe a debounce ("Changes closer than 100 ms count as one", client.mdx#L51, server.mdx#L33), not this behavior.
Found by reading the code path (not reproduced).
Expected: one reload or restart after the last change of a burst.
Suggested fix: a trailing debounce (reset a setTimeout on each event), one timer per watched folder.
Found during a read-only audit of main @ 044c766 (2026-11-11).
Code sample
let lastCall = Date.now();
const onClientWatch = () => {
if (lastCall + 100 > Date.now()) return; // drops the rest of the burst
lastCall = Date.now();
server.publish("watch", "update"); // fires on the first event
};
Versions
- @nanoforge-dev/loader-client / @nanoforge-dev/loader-server / @nanoforge-dev/loader-website 1.7.0 (
main@ 044c766) - Bun 1.3.14
- Linux x86_64
Issue priority
Medium (should be fixed soon)
I have tested this issue on a development release
044c766
- 主要語言
- TypeScript
- 星號
- 1
- 分支
- 0
- 平均合併
- 17 小時 25 分鐘
- 30 天內合併 PR
- 11
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
NanoForge-dev/Loader 的其他 Issue
-
app:client app:website enhancement refactor
難度 2/5 1-3 小時 新手友好度 72/100
NanoForge-dev/Loader#145 ·
維護者通常 1 天內回覆
-
chore(loader-client,loader-server): package.json entry points name files the build does not produce未關閉app:client app:server bug chore good first issue
難度 2/5 1-3 小時 新手友好度 78/100
NanoForge-dev/Loader#144 ·
維護者通常 1 天內回覆
-
app:website bug good first issue
難度 2/5 1-3 小時 新手友好度 85/100
NanoForge-dev/Loader#141 ·
維護者通常 1 天內回覆
-
app:website bug good first issue
難度 2/5 1-3 小時 新手友好度 82/100
NanoForge-dev/Loader#140 ·
維護者通常 1 天內回覆
-
app:server bug
難度 2/5 1-3 小時 新手友好度 85/100
NanoForge-dev/Loader#138 ·
維護者通常 1 天內回覆
查看 NanoForge-dev/Loader 的全部 Issue
相似的 Issue
-
Mend: dependency security vulnerability
難度 1/5 1-3 小時 新手友好度 65/100
fdm-monster/fdm-monster#5563 ·
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 72/100
be-BOP-io-SA/be-BOP#2849 ·
-
難度 2/5 1-3 小時 新手友好度 79/100
維護者通常 1 天內回覆
-
1️⃣ phase/under-investigation flaky/confirmed flaky/needs-decision type/bug
難度 2/5 1-3 小時 新手友好度 65/100
growilabs/growi#12246 · 3 則留言 ·
維護者通常 1 天內回覆
-
🐛 The Rulekeeper - An index run that gives up on the lock ends Succeeded可能已有人在做 @github-actions 今天認領。 未關閉
難度 2/5 1-3 小時 新手友好度 72/100
SSWConsulting/SSW.Rules#2809 · 1 則留言 ·
維護者通常 1 天內回覆