Skip to main content
bmux isn’t on npm yet, so npm install -g bmux won’t work. Build it from source with the steps below — it takes about a minute.

Requirements

The CLI depends on sharp, which ships prebuilt binaries for Linux, macOS and Windows. There’s nothing to compile.
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 it again

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.