Install zx with Homebrew, apt, Nix

Project links

• Homepage

Commands and aliases

• zx

Project history

The google/zx repository began in May 2021, with Anton Medvedev listed as package author. Its core idea is the `$` tagged template: commands look shell-like, but arguments are escaped and execution is wrapped in a ProcessPromise API rather than raw child_process boilerplate.

The project evolved from a Node-oriented helper into a broader runtime tool. The README now documents Linux, macOS, and Windows support plus Node, Bun, Deno, and GraalVM compatibility; later documentation added TypeScript, markdown scripts, remote scripts, dependency auto-installation, and a lighter zx@lite entry point.

Adoption history

zx spread quickly because it hit a common pain point for JavaScript-heavy teams: build, release, migration, and glue scripts often outgrow bash, but plain Node scripts are verbose for process execution. Its GitHub repository has tens of thousands of stars, and the package became recognizable enough to be installed both from JavaScript tooling and system package managers.

The adoption pattern is strongest around project-local automation rather than end-user CLI apps. Teams use zx when they want scripts to live beside package.json, call existing Unix tools, await concurrent commands, and reuse npm libraries without switching to a task runner framework.

How it is used

A zx script is commonly run with `zx script.mjs`, `npx zx`, a shebang using `/usr/bin/env zx`, or a package.json script. The CLI can execute ordinary files, extensionless scripts, markdown code blocks, stdin, eval snippets, and remote URLs, while flags control shell choice, verbosity, local dependency preference, and on-demand package installation.

In practice zx is used for release scripts, deployment wrappers, repository maintenance, monorepo chores, code-generation glue, CI helpers, and one-off administrative scripts where the author wants shell commands plus JavaScript data handling.

Why package nerds care

zx is package-nerd significant because it blurred the line between a language package and a system scripting tool. It made `npm install zx` feel like installing a better shell harness, and it became a reference point for the idea that developer automation can be distributed as a normal package while still acting like a Unix command.

Timeline

• 2021-05: google/zx public git history starts.
• 2021-05: Early 1.x releases establish the `$` template shell API.
• 2022-03: 6.0.0 release era adds broader CLI packaging and workflow polish.
• 2024-04: 8.0.0 release era continues the modern runtime and TypeScript-focused evolution.
• 2025-10: GitHub lists 8.8.5 as a recent release, with ongoing maintenance.

Related projects

• Node.js child_process: the standard library surface zx wraps for scripts.
• Bash and PowerShell: the shells zx invokes rather than fully replacing.
• Bun and Deno: alternative JavaScript runtimes supported by current zx documentation.

Sources

• https://github.com/google/zx
• https://google.github.io/zx/cli
• https://google.github.io/zx/getting-started
• https://raw.githubusercontent.com/google/zx/main/package.json