fix(loader-client,loader-server): the watchers throttle on the first event instead of debouncing

Abierto
  • ¿Algo no está bien?
#136 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
70/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
bun, typescript
Área
devtools

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

app:client app:server bug
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 one lastCall, 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

Lenguaje dominante
TypeScript
Estrellas
1
Forks
0
Merge medio
17 h 25 min
PR fusionados (30 d)
11

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de NanoForge-dev/Loader

Todos los issues de NanoForge-dev/Loader

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.