Updating blxbench

The same package you installed globally is @bitslix/blxbench (see Installation). Pick the tool you used the first time — that keeps the global install layout consistent on your machine.

Using npm

npm install -g @bitslix/blxbench@latest
# short form, same result:
npm update -g @bitslix/blxbench

@latest pulls the current release line from the npm registry.

Using pnpm

pnpm add -g @bitslix/blxbench@latest
# or, if pnpm is managing that global:
pnpm update -g @bitslix/blxbench

Using Bun

bun install -g @bitslix/blxbench@latest
# or, when bun tracks the global package by name:
bun update -g @bitslix/blxbench

Check the version

blxbench --version
# or: blxbench -V

In the interactive TUI, the top bar shows v<version> next to the name so you can confirm what is running. After an update, open a new terminal (or new blxbench session) so the shell picks up the new binary on PATH.

In-app “newer on npm” notice (TUI)

When you start blxbench without headless mode, the shell can compare your build to the version published for @bitslix/blxbench on the npm registry (same source as the website’s Download and Changelog flow).

• If a newer release is available, you will see a cyan-bordered info box under the header (different from the yellow “not signed in” banner).
• It is safe to ignore when offline: no network or registry hiccup means no box.
• Updating is the same as above: reinstall or update the global package; you do not need a separate “blxbench component” beyond @bitslix/blxbench.

Release notes

See What’s new (changelog) for user-facing changes between versions.

Same machine, from source (optional)

If you build from the repository instead of npm, pull the latest tag or main, then rebuild with your monorepo workflow; that path does not use the public registry version on disk, so the TUI’s npm comparison is most meaningful when you use the published global install.