Install wren-cli with Homebrew, MacPorts

Project links

• Homepage
• Upstream docs
• Package manager page

Commands and aliases

• wren_cli

Project history

The Wren language repository dates to 2013, and the language site describes Wren as a small, fast, class-based concurrent scripting language with an intentionally tiny implementation and standard library. In November 2018 Bob Nystrom announced that Sven Bergstrom, known as ruby0x1, would become Wren's lead maintainer and that the project would move under the `wren-lang` organization, preserving issues, pull requests, and project infrastructure.

The Wren development blog announced the maintainer transition publicly on 4 February 2019 and emphasized continuity: Wren would evolve while staying small, simple, learnable, and hackable. The separate `wren-cli` repository was created later in 2019 as the standalone command-line tool for the language, and GitHub releases show tagged CLI releases such as 0.3.0 in June 2020 and 0.4.0 in November 2021.

Adoption history

Wren's adoption has historically centered on embedding, games, language experimentation, and small tools rather than a large package ecosystem. The Wren homepage highlights the small VM and C API, while the CLI page frames wren-cli as both a practical tool and a real-world usage example for people learning how Wren can be embedded and extended.

The CLI also reflects Wren's post-2018 stewardship model: the language and supporting tools live in the shared `wren-lang` organization instead of only under the original author's account. That makes wren-cli part of the maintained Wren distribution story even though it is intentionally separate from the minimal core VM.

How it is used

Users install or build `wren_cli` to run Wren source files, start a REPL, and access the CLI-specific modules documented at `wren.io/cli`. The CLI depends on libuv for operating-system features, which lets scripts use facilities such as file I/O and networking while keeping the base Wren language small.

Typical package-nerd usage is exploratory: run examples, test snippets, wire small scripts, or compare Wren's embedding model with Lua-style scripting. The CLI page is explicit that it is a work in progress and a standalone project, so users should treat it as the general-purpose executable around the language rather than as the entire Wren runtime.

Why package nerds care

wren-cli is significant because it packages the otherwise embeddable-first Wren VM into a normal Unix-style executable. That makes it indexable by Homebrew and MacPorts, scriptable from a shell, and easy to include in language-runtime inventories alongside Lua, Janet, or other compact embeddable languages.

Its separation from the core language is also historically interesting: Wren's design keeps the VM and standard library small, while the CLI carries the pragmatic I/O surface that package users expect from a runnable scripting language.

Timeline

• 2013: The Wren language repository is created on GitHub.
• 2018: Bob Nystrom announces a maintainer transition and move to the `wren-lang` organization.
• 2019-02-04: The Wren blog announces the new maintainer era and centralized project blog.
• 2019-09-18: The `wren-lang/wren-cli` repository is created.
• 2020-06-05: Wren CLI 0.3.0 is published on GitHub.
• 2021-11-20: Wren CLI 0.4.0 is published on GitHub.

Related projects

• Wren is the core language and VM that wren-cli runs.
• libuv supplies the CLI's operating-system-facing functionality.
• The wren-lang organization hosts the language, CLI, and site repositories.

Sources

• https://api.github.com/repos/wren-lang/wren
• https://api.github.com/repos/wren-lang/wren-cli
• https://api.github.com/repos/wren-lang/wren-cli/releases
• https://groups.google.com/g/wren-lang/c/cMUwij-NIn0
• https://wren.io/
• https://wren.io/blog/0-hello-wren.html
• https://wren.io/cli/