nf build --watch wipes the browser server build on each client rebuild in p2p mode

Abierto
  • ¿Algo no está bien?
#278 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
72/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
bun, node.js, typescript
Área
build-system

Línea de trabajo

Read src/action/actions/build.action.ts, especially the p2p browser server output configuration at lines 74–82 and the watch rebuild flow around resetOut at line 139. Trace how client and server targets are scheduled on rebuild, then check whether a client rebuild preserves or rebuilds the browser server output. Done means the server app remains available after client changes in watch mode.

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

Descripción

bug command:build
Which package is this bug report for?

@nanoforge-dev/cli

Which command is this bug report for?

build

Issue description

In a peer-to-peer workspace (network: "p2p"), nf build --watch deletes the browser build of the server app every time the client rebuilds (read from the code, not run).

The browser server target writes into <client out>/server (src/action/actions/build.action.ts#L74-L82). In watch mode each target rebuilds on its own, and each rebuild first runs resetOut(target.output) (src/action/actions/build.action.ts#L139). A change under the client's entry folder therefore deletes <client out>/server. It only comes back when a file in the server's entry folder changes, so until then the host's browser loads the game without its server app.

#244 ordered the server build after the client build "since that one resets the output". That works for a one-off build, but not for watch rebuilds.

Expected: in p2p mode, a client rebuild is followed by a rebuild of the browser server targets (or a client rebuild leaves the server/ subfolder alone).

Found during a read-only audit of main at e95b881 (2026-11-11).

Code sample
output: relative(server.directory, join(client.directory, client.output, "server")),
// ...
const executeBuild = (rebuild = false) =>
  runSafe(() => { this.resetOut(target.output, target.directory); /* ... */ });
Versions
  • @nanoforge-dev/cli 3.0.1 (main, e95b881)
  • Node.js 26.7.0
  • Bun 1.3.14 (bundled)
  • Linux
Issue priority

Medium (should be fixed soon)

I have tested this issue on a development release

No response

Lenguaje dominante
TypeScript
Estrellas
2
Forks
2
Merge medio
2 d 18 h
PR fusionados (30 d)
17

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/CLI

Todos los issues de NanoForge-dev/CLI

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.