Skip to main content
Install @bluejutzu/bmux, which puts bmux on your PATH.
Requires Node 20 or newer. The CLI depends on sharp, which ships prebuilt binaries for Linux, macOS and Windows, so there’s nothing to compile — installing just works.

​
Removing it again

​
Unreleased builds

Every push to master packs and attaches the CLI tarball to its CI run, so you can pick up a fix before it’s tagged. Open the latest CI run, scroll to Artifacts, and download bmux-<sha>.
GitHub wraps workflow artifacts in a .zip. Unzip it to get the .tgz inside, then install it like any local package:

​
Building from source

For working on bmux itself, or trying an unreleased change.

​
Requirements

1

Clone and install

2

Build

The CLI depends on @bmux/core’s build output, so build the whole workspace rather than just the CLI package.
3

Put bmux on your PATH

This symlinks the package, so it keeps pointing at your checkout — rebuild and the bmux command picks the change up immediately.
4

Check it worked

​
Removing the linked build

​
Without linking

If you’d rather not put anything on your PATH, run the built entry point directly:
That’s the same binary the linked bmux command runs.

​
Paths on Windows

Both separators work:
PowerShell doesn’t expand globs itself, so quote them and let bmux do the matching — bmux convert "photos/*.png" --to webp

​
Exit codes

A failed file never cancels the others — the batch runs to the end, then exits non-zero. That’s what makes it safe to drop into CI.