@nwire/cli 0.13.0 → 0.13.1

package/dist/lib/dev-host.js

@@ -46,6 +46,7 @@ import { createRequire } from "node:module";
 import sirv from "sirv";
 import { createServer as createViteServer } from "vite";
 import { createStudioHostApi } from "./studio-host-api.js";
+import { ensureScanFresh } from "./ensure-scan.js";
 // ── Active-endpoint selection helpers ────────────────────────────────────────
 /**
  * Determine which mount should front the HTTP surface.
@@ -267,6 +268,17 @@ export async function startDevHost(opts) {
         // (workers/cron/non-HTTP) still run in-process and are observable via
         // telemetry + manifest.
         adoptMount(active);
+        // Build/refresh `.nwire/manifest.json` so Studio's manifest-backed pages
+        // (Map, Trace, Plugins, schemas…) have data from the first request and stay
+        // current across HMR reloads. Static scan + topology fold — no app boot of
+        // its own; fingerprint-gated so an unchanged tree is a near no-op. A scan
+        // failure must never take down the dev host, so it's best-effort.
+        try {
+            await ensureScanFresh(opts.cwd, { quiet: true });
+        }
+        catch {
+            // manifest stays as-is; Studio data pages degrade, the wire keeps serving.
+        }
     }
     // Initial load — boot the wire for the first time.
     await loadEntry();

package/dist/lib/studio-host-api.js

@@ -82,11 +82,12 @@ function sseWrite(res, event, data) {
  * GET /__nwire/manifest.json
  *
  * Serves the disk-built `.nwire/manifest.json`. When a live runtime is
- * present the static file already reflects the last `nwire cache` run;
- * the intent for future increments is to fold live handler registrations
- * from the runtime so the manifest stays accurate during HMR. Today the
- * disk file is served verbatim (the same as standalone Studio) — this is
- * correct: `nwire dev` runs `nwire cache --if-stale` at boot.
+ * present the static file already reflects the source tree as of the last
+ * scan; the intent for future increments is to fold live handler
+ * registrations from the runtime so the manifest stays accurate during HMR.
+ * Today the disk file is served verbatim (the same as standalone Studio) —
+ * the dev host calls `ensureScanFresh` on each (re)load so the file exists
+ * from the first request and tracks source edits across HMR.
  *
  * A `?force=true` query param is reserved for a future "rebuild" button
  * trigger but is not acted on here (that requires spawning `nwire cache`).

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nwire/cli",
-  "version": "0.13.0",
+  "version": "0.13.1",
   "description": "Nwire CLI — branded TUI. Dev, run, please, build, test, fmt, lint, check, ps, logs, cache, ls, studio. One surface for the whole framework.",
   "keywords": [
     "cli",
@@ -37,10 +37,10 @@
     "react": "^18.3.1",
     "sirv": "^3.0.1",
     "vite": "npm:rolldown-vite@latest",
-    "@nwire/endpoint": "0.13.0",
-    "@nwire/hooks": "0.13.0",
-    "@nwire/scan": "0.13.0",
-    "@nwire/mcp": "0.13.0"
+    "@nwire/endpoint": "0.13.1",
+    "@nwire/hooks": "0.13.1",
+    "@nwire/mcp": "0.13.1",
+    "@nwire/scan": "0.13.1"
   },
   "devDependencies": {
     "@types/node": "^22.19.9",