@unotest/viewer 0.14.0 → 0.16.0

package/CHANGELOG.md

@@ -1,5 +1,68 @@
 # Changelog
 
+## [0.16.0] - 2026-08-19
+
+### Minor Changes
+
+- 1327a52: Capability-aware UI when the viewer runs behind a proxy.
+
+  New `GET /api/session` reports what the current session may do
+  (`canRun` / `canEditFiles` / `canTerminal` / `canBrowseFs`) plus a
+  display-only identity. A fronting proxy stamps the answer on every
+  request it forwards via the `x-unotest-viewer-session` header; the
+  contract and its codec ship as the new `@unotest/viewer/session`
+  subpath export.
+
+  The frontend greys out Run/Debug, the terminal (button AND the ⌃`
+  chord), scenario/collection/snapshot mutations and the Save button when
+  the session lacks the matching capability, and the status bar names the
+  session with a Log out entry.
+
+  No change for plain localhost usage: with no header the endpoint answers
+  full capabilities and no identity, and a failed lookup keeps the UI
+  permissive. The viewer still authorizes nothing itself — the header can
+  only narrow what the UI offers, never grant access.
+
+### Patch Changes
+
+- Updated dependencies [bf92e6f]
+  - @unotest/dsl@0.16.0
+  - @unotest/protocol@0.16.0
+
+## [0.15.0] - 2026-08-17
+
+### Minor Changes
+
+- 32692b4: Make `node-pty` an optional dependency. It is a native addon with no prebuilt
+  binary for every platform — linux-arm64 among them — so on a machine without a
+  C/C++ toolchain npm compiled it from source and the whole install died with a
+  node-gyp error, before anything of ours was on disk. It backs one panel, the
+  docked terminal, which most runs never open.
+
+  It is now loaded on first use rather than at import time, so its absence is a
+  state the viewer reports instead of a crash it takes: the server starts, runs
+  and scenarios and the editor work, and the terminal panel explains what is
+  missing, what still works, and how to enable it.
+
+### Patch Changes
+
+- d2161a9: Fix the standalone `unotest-viewer` bin, which started nothing. It imported
+  `dist/server/main.js` for its side effect, but that module self-starts only
+  when node was pointed at it directly — launched through the bin the check was
+  false, so the process exited 0 with no output, no error and no server. The bin
+  now calls the exported `runViewerCli()`.
+
+  `npx @unotest/web viewer` was never affected: it imports `@unotest/viewer/server`
+  and calls `startViewerServer()` itself. That import must stay side-effect free,
+  so the entry-point check stays — the bin just no longer depends on it.
+
+  A build-time smoke (`smoke:bin`) now starts the built bin, fetches the URL it
+  reports and kills it, because the failure mode here is silence: a bin that
+  exits 0 and serves nothing passes every check that only looks at exit codes.
+
+  - @unotest/dsl@0.15.0
+  - @unotest/protocol@0.15.0
+
 ## [0.14.0] - 2026-08-16
 
 ### Patch Changes

package/bin/unotest-viewer.js

@@ -3,5 +3,11 @@
 // invoke this — `npx @unotest/web viewer` is the canonical entry that
 // spawns the same server. Kept here for dev / debug / future Electron
 // builds that embed Nest directly.
+//
+// Calls the exported function rather than importing the module for its
+// side effect: main.js only self-starts when node was pointed AT it, so
+// a bare import from here started nothing and exited 0 in silence.
 
-import "./../dist/server/main.js";
+import { runViewerCli } from "./../dist/server/main.js";
+
+await runViewerCli();

package/dist/server/main.d.ts

@@ -43,5 +43,17 @@ interface ViewerHandle {
 /** Public entry — `@unotest/web`'s viewer subcommand calls this via
  *  `await import('@unotest/viewer/server').startViewerServer({...})`. */
 declare function startViewerServer(opts: StartViewerOptions): Promise<ViewerHandle>;
+/** Standalone launch: read the environment, start the server, stay up
+ *  until a signal. Exported because `bin/unotest-viewer.js` has to CALL
+ *  it — importing this module and hoping the entry-point check below
+ *  fires is what the bin used to do, and the check is false when node
+ *  was pointed at the bin (argv[1] is the bin, not this file). The
+ *  server never started and the process exited 0, saying nothing.
+ *
+ *  No caller injects runners here, so `startViewerServer` auto-detects
+ *  the installed `@unotest/*` runner packages (by name — DIP boundary
+ *  intact). `UNOTEST_RUNNER_PKG` (legacy single-runner var) and
+ *  `UNOTEST_TARGET` just pick which detected target is active at boot. */
+declare function runViewerCli(): Promise<void>;
 
-export { type RunnerEntry, type StartViewerOptions, type ViewerHandle, startViewerServer };
+export { type RunnerEntry, type StartViewerOptions, type ViewerHandle, runViewerCli, startViewerServer };