@bitslix/blxbench-report-browser
v1.3.4
Published
BLXBench report browser — native desktop app (Tauri), optional install for the blxbench CLI via npm.
Readme
@bitslix/blxbench-report-browser
Native desktop app (Tauri) for BLXBench reports under ~/.blxbench/reports. The published npm metapackage pulls a platform-specific binary (Linux x64, macOS arm64/x64, Windows x64) as an optional dependency — the same layout as @bitslix/blxbench.
Install (with blxbench CLI)
From the TUI (Bencher / Founder / Admin):
/report browser install
/report browser openOr manually:
npm install --prefix ~/.blxbench/lib/report-browser @bitslix/blxbench-report-browserThat installs the metapackage — including bin/blxbench-report-browser.js (same launcher pattern as the main CLI’s bin/blxbench.js: resolve optional native binary, chmod if npm dropped +x, then run Tauri) — plus the optional @bitslix/blxbench-report-browser-<platform> binary. /report browser open runs that launcher when present.
Override: set BLXBENCH_REPORT_BROWSER_BINARY to a blxbench-report-browser executable you built locally.
Monorepo development
- Web UI (Vite):
pnpm --filter @bitslix/blxbench-report-browser run dev/run build— used by Tauri’sbeforeBuildCommand; not published to npm anymore. - Desktop:
pnpm --filter @bitslix/blxbench-report-browser tauri dev/tauri build. - Legacy local HTTP preview (optional): after
pnpm run build, you can still runnode bin/blxbench-report-browser.js --no-openfrom this directory for debugging only; it is not part of the npm product path.
Release
See RELEASING.md and the GitHub workflow publish-report-browser-npm-reusable.yml: build native per OS, publish the four @bitslix/blxbench-report-browser-* packages, then publish the metapackage (manifest strips dev-only fields).
API prefix
The embedded webview loads the Vite build; dev calls may use GET under /__blx/... (see src/lib/report-invoke.ts).
License
MIT — see LICENSE.
