Install luarocks with Homebrew, apk, chocolatey, apt, dnf, Nix, pacman, scoop

Project links

• Homepage
• Repository
• Upstream docs
• Package manager page

Commands and aliases

• luarocks
• luarocks-admin

Project history

The LuaRocks project describes itself as the package manager for the Lua programming language. Its repository README and wiki say it installs modules as self-contained packages called rocks and supports local and remote repositories plus multiple local rocks trees.

LuaRocks' documentation centers on the rockspec: a Lua metadata file that tells the tool how to fetch, build, and install a package. This design made LuaRocks both a package installer and a lightweight build/publishing convention for Lua modules, including modules with native C extensions.

Adoption history

LuaRocks became the default package-distribution culture for much of Lua outside application-specific ecosystems. The official site surfaces recent modules, labels, weekly download counts, root manifests, custom manifests, mirrors, and upload flows, showing that LuaRocks is both a CLI and the central package index.

The input metadata shows broad OS package coverage: LuaRocks is available through Homebrew, MacPorts, Debian, Ubuntu, Fedora, Alpine, Arch, Nix, Scoop, and Chocolatey. That matters because Lua projects often need LuaRocks before they can install testing tools, web frameworks, OpenResty libraries, or native-binding modules.

How it is used

The command-line interface is luarocks. It supports installing, building, packing, uploading, searching, showing, removing, testing, and configuring rocks, and can operate against selected servers, trees, and dependency modes.

Package authors write a rockspec, tag or publish their source, and submit or upload the rockspec. LuaRocks can build from source, make from a local checkout, pack source or binary rocks, and publish artifacts that users install without needing the original source-control tool.

Why package nerds care

LuaRocks is central package-nerd infrastructure for Lua because it defines the names, versions, build metadata, binary/source artifact formats, and repository manifests that other tools consume. It is the closest analogue to npm, RubyGems, or CPAN for Lua, but with Lua-specific details such as Lua-version-specific trees and native module paths.

It is also historically important because it works across stock Lua and LuaJIT ecosystems. That cross-runtime support, plus package-manager availability on Unix and Windows, made it the practical bootstrap path for Lua dependency management.

Timeline

• 2000s: LuaRocks emerges as Lua's rockspec-based package manager.
• 2010s: Development and distribution consolidate around the GitHub repository and luarocks.org.
• 2020s: Documentation moves from the GitHub wiki into the repository docs folder.
• 2026: GitHub lists LuaRocks 3.13.0 as the latest release, dated Jan 28, 2026.

Related projects

• Lua is the language ecosystem LuaRocks packages target.
• LuaJIT is a common LuaRocks runtime target and package dependency.
• OpenResty libraries such as lua-resty modules are commonly distributed through LuaRocks.

Sources

• https://github.com/luarocks/luarocks
• https://github.com/luarocks/luarocks/blob/main/docs/config_file_format.md
• https://github.com/luarocks/luarocks/blob/main/docs/creating_a_rock.md
• https://github.com/luarocks/luarocks/blob/main/docs/luarocks.md
• https://luarocks.org/
• https://luarocks.org/docs
• source_facts.package-manager