Install xplr with Homebrew, apk, MacPorts, Nix, pacman, zypper

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• xplr

Project history

The project appeared in the early 2020s as a TUI file explorer in the same cultural space as nnn, fzf, ranger-like panes, and Neovim-style keyboard workflows. Its README says xplr is not meant to replace standard shell commands or GUI file managers, but to integrate them through a scriptable terminal interface.

A key turning point was the v0.10 era in May 2021, when maintainer Sayanarijit announced that xplr had moved away from YAML and embraced embedded LuaJIT, explicitly citing Neovim as an inspiration. The stated reasons were portability, safer customization than shell snippets, richer scriptability, speed, and a plugin community model.

The official upgrade guide marks v1.0.0 as the first stable release and says xplr v1 could be considered feature complete, with no immediate plan for v2. Subsequent development has focused on maintenance, performance, and incremental ergonomic features rather than repeatedly reshaping the tool.

Adoption history

xplr adoption is strongest among terminal-heavy users who want a visual navigator without leaving shell composition behind. The README points to Homebrew, crates.io, documentation, hacks, plugins, integrations, reviews, and Repology packaging, showing a project whose ecosystem is as much about configuration and plugins as the core binary.

The official docs list many plugins and integrations: dual-pane and tri-pane layouts, fzf integration, clipboard support, terminal integration, tree view, disk-usage tools, drag-and-drop helpers, and a plugin manager. That is the real adoption story: users extend xplr into their terminal workflow rather than treating it as a fixed file manager.

How it is used

Users launch xplr inside a directory, navigate with modal key bindings, select paths, and either perform built-in file operations or hand paths to external commands. It can print selected paths or the current directory on quit, which makes it useful inside shell aliases and editor workflows.

Configuration lives in Lua, usually at ~/.config/xplr/init.lua. The documented model exposes modes, messages, key bindings, layouts, hooks, and Lua function calls, so practical use often becomes a small personal TUI environment rather than a stock file browser.

Why package nerds care

xplr is a good example of the post-2010s terminal renaissance: Rust implementation, TUI ergonomics, Lua customization, Neovim influence, fzf-style searching, and package-manager distribution all in one small binary.

For package catalogs, it sits between classic file managers and programmable launchers. Its significance is not mass desktop adoption; it is the way it packages a hackable terminal workflow that expects to collaborate with other command-line tools.

Timeline

• 2021-04-15: An early public tag, v0.4.4, is visible in repository history.
• 2021-05-23: The maintainer announced the v0.10 move from YAML to embedded LuaJIT.
• 2022-10-28: v0.20.0 entered the long 0.20/0.21 maturation period.
• 2025-03-21: v1.0.0 was published as the first stable, feature-complete v1 release.
• 2025-12-08: v1.1.0 shipped with no breaking changes and performance improvements for large directories.

Related projects

• nnn and fzf: terminal-navigation influences and related tools mentioned by the xplr community.
• Neovim: the explicit model for embedding Lua to grow a customization and plugin ecosystem.
• ranger-style pane file managers: a neighboring workflow represented by xplr plugins such as tri-pane.xplr.

Sources

• https://github.com/sayanarijit/xplr
• https://github.com/sayanarijit/xplr/discussions/183
• https://github.com/sayanarijit/xplr/releases/tag/v1.0.0
• https://github.com/sayanarijit/xplr/releases/tag/v1.1.0
• https://xplr.dev/en/awesome-plugins
• https://xplr.dev/en/introduction
• https://xplr.dev/en/upgrade-guide