Installer ammonite-repl avec Homebrew

Liens du projet

• Page d'accueil
• Dépôt
• Page du gestionnaire de paquets

Commandes et alias

• amm

Historique du projet

The public GitHub repository was created in January 2015 and describes the project as 'Scala Scripting'. The codebase contains the `amm` launcher, REPL and script-runner implementation, a terminal/JLine reimplementation used for interactive editing, integration tests, and Scalatex-generated documentation.

Ammonite's design centered on replacing the rough edges of the stock Scala REPL with syntax highlighting, multiline editing, direct Maven artifact imports, pretty output, and `.sc` script execution. Its documentation frames the goal as freeing small Scala programs from heavyweight projects and avoiding the startup cost of tools such as sbt for quick scripting work.

Release and publishing notes in the upstream README describe stable releases from tagged commits and unstable artifacts from every commit on the main branch. The latest GitHub release observed for this batch is 3.0.9, published in March 2026.

Historique d'adoption

Ammonite became a familiar tool in the Scala command-line ecosystem because it gave Scala developers a batteries-included REPL and script runner before similar comforts were widely available upstream. The official README points users to the Gitter channel, Patreon, and the author's Hands-on Scala material, whose examples make extensive use of Ammonite.

Package-manager adoption reflects that CLI role: the Homebrew formula provides `ammonite-repl` and installs the `amm` executable. Its historical packaging matters because developers commonly reached for Ammonite from a shell, not only as a library dependency.

Modes d'utilisation

Users run `amm` to open the REPL or execute `.sc` scripts. Common documented customization points are predef files under `~/.ammonite`, including `predef.sc` for the interactive REPL and `predefScript.sc` for scripts.

Ammonite's package-nerd usage pattern was often 'install one executable, import Maven coordinates inline, and script in Scala'. That made it attractive for one-off automation, exploratory data work, library experiments, and examples where a full sbt project would be slower to create than the code itself.

Pourquoi les passionnés de paquets s'y intéressent

Ammonite is a useful case study in how an alternate REPL can pressure a language ecosystem: its conveniences eventually became expected behavior, and upstream Scala later absorbed many of them.

For package maintainers, it is also the kind of language tool whose value is in the launcher, cache, and per-user startup files as much as in the compiler integration. Correct packaging gives users a real `amm` command with predictable home-directory behavior.

Chronologie

• 2015: GitHub repository created for Ammonite.
• 2015-2020s: Ammonite grows as a Scala REPL, script runner, and shell-friendly alternative to creating sbt projects for small programs.
• 2026: Upstream release 3.0.9 is published.
• Current upstream docs: Ammonite is marked deprecated, with Scala scripting users directed to Mill and REPL features noted as moving upstream.

Related projects

• Scala REPL: upstream REPL that later received several Ammonite-style quality-of-life features.
• Mill: Li Haoyi's build tool, now recommended by Ammonite docs for Scala single-file scripting.
• sbt: the traditional Scala build tool whose startup and project overhead Ammonite often avoided for small tasks.

Sources

• https://ammonite.io/
• https://api.github.com/repos/com-lihaoyi/Ammonite
• https://api.github.com/repos/com-lihaoyi/Ammonite/releases/latest
• https://github.com/com-lihaoyi/Ammonite
• https://github.com/com-lihaoyi/Ammonite#readme
• source_facts.executables
• source_facts.package-manager