# Install closure-compiler with Homebrew, apt JavaScript optimizing compiler. Version 20260629 via Homebrew; verified 2026-07-01. ## Install ```sh sudo av install brew:closure-compiler ``` Additional install commands: ### macOS - Homebrew (100%): ```sh brew install closure-compiler ``` Evidence: local Homebrew formula metadata ### Linux - Debian apt (92%): ```sh sudo apt install closure-compiler ``` Evidence: Debian stable package indexes: closure-compiler from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz ## Package facts - **Package key:** brew:closure-compiler - **Package manager:** Homebrew - **Package manager page:** - **Version:** 20260629 - **Source summary:** JavaScript optimizing compiler - **Homepage:** - **Repository:** - **Upstream docs:** - **License:** Apache-2.0 - **Source archive:** - **Last updated:** 2026-07-01T00:07:44Z - **Generated:** 2026-07-08T07:18:31+00:00 ## Executables - closure-compiler (cli) - closure-compiler (alias) ## Dependencies - openjdk ## Install behavior - Post-install hook: not defined - Bottle: available on all ## Freshness - Page generated: 2026-07-08 - Package-manager version: 20260629 - Package-manager updated: 2026-07-01 - Local data: ok - Upstream repository: https://developers.google.com/closure/compiler - info: Release/tag comparison is only available for GitHub repositories. ## Project history and usage Closure Compiler is Google's JavaScript checker and optimizer, descended from the Closure Tools release that made Google's internal large-scale JavaScript tooling available to external developers. Its package-manager story is unusual because the compiler is a Java project with Maven distribution, npm wrappers, and OS package formulas rather than a single canonical CLI channel. ### Project history Google introduced Closure Tools in 2009, including Closure Compiler, Closure Library, Closure Templates, and Closure Inspector. The compiler's role was to parse JavaScript, perform type and syntax checks, remove dead code, and rewrite code for smaller downloads and faster execution. The current GitHub repository is maintained by Google and documents the compiler as a whole-program optimizer whose strongest mode, ADVANCED, expects code written with Closure Compiler's assumptions in mind. The README also records the project's long relationship with Closure Library style modules and its more limited fit with modern arbitrary JavaScript bundles. ### Adoption history Google's launch post tied Closure Tools to JavaScript-heavy products such as Gmail, Google Docs, and Google Maps, which made the compiler historically important as a public version of infrastructure used in large browser applications. Distribution broadened beyond direct Java JAR usage: the upstream README points to Maven artifacts and notes npm/Yarn installation through the separate google-closure-compiler npm packaging maintained outside Google. The Homebrew, Debian, and Ubuntu package-manager facts in the input show that the CLI also became a conventional system package. ### How it is used Typical CLI use compiles one or more JavaScript inputs to an output file, with SIMPLE or ADVANCED optimization levels. The compiler can also check types and conformance, transpile newer JavaScript for older browsers, emit source maps, and split output into loadable chunks. The project is best treated as a specialized optimizer for codebases prepared for its rules, especially when property renaming, externs, and Closure-style module conventions matter. ### Why package nerds care Closure Compiler matters to package nerds because it crosses packaging cultures: Java artifacts, npm command wrappers, Linux distro packages, and Homebrew all expose the same optimizer with different expectations about runtime, update cadence, and command names. It is also a useful example of a package whose canonical upstream warns that one popular distribution path, npm, is built by an outside maintainer from a separate repository, so package provenance matters. ### Timeline - 2009: Google introduced Closure Tools and open sourced Closure Compiler. - 2014: The current google/closure-compiler GitHub repository metadata was created. - 2024: The README documented deprecation or reduced support for some non-ADVANCED and non-Closure-style module paths. ### Related projects - Closure Library, Closure Templates, and Closure Inspector were announced with Closure Compiler as related Closure Tools. - closure-compiler-npm is the separate npm packaging repository named by the upstream README. - Modern JavaScript bundlers and minifiers overlap with Closure Compiler in SIMPLE-style minification, while Closure Compiler remains distinctive as a whole-program optimizer. ### Sources - - - ## Security Notes No matching local secret-handling manifest was found for closure-compiler. Nucleus package metadata is still published here so future coverage has a stable package URL. ## Source Database Details - **Source Database:** Homebrew formula API - **Tap:** homebrew/core - **Full Name:** closure-compiler - **Version Scheme:** 0 - **Revision:** 0 - **Bottle Stable Root URL:** - **Deprecated:** no - **Disabled:** no - **Keg Only:** no - **URL Keys:** stable ## Other Package-Manager Records - Debian apt - closure-compiler - 20130227+rhino-2: normalized package name match | Debian stable package indexes: closure-compiler from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | JavaScript optimizing compiler | https://developers.google.com/closure/compiler/ - Debian apt - libclosure-compiler-java - 20130227+rhino-2: normalized package name match | Debian stable package indexes: libclosure-compiler-java from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | JavaScript optimizing compiler - library package | https://developers.google.com/closure/compiler/ - Debian apt - libclosure-compiler-java-doc - 20130227+rhino-2: normalized package name match | Debian stable package indexes: libclosure-compiler-java-doc from https://deb.debian.org/debian/dists/stable/main/binary-amd64/Packages.xz | JavaScript optimizing compiler - Javadoc | https://developers.google.com/closure/compiler/ - Ubuntu apt - closure-compiler - 20130227+rhino-2: normalized package name match | Ubuntu 24.04 LTS package indexes: closure-compiler from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | JavaScript optimizing compiler | https://developers.google.com/closure/compiler/ - Ubuntu apt - libclosure-compiler-java - 20130227+rhino-2: normalized package name match | Ubuntu 24.04 LTS package indexes: libclosure-compiler-java from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | JavaScript optimizing compiler - library package | https://developers.google.com/closure/compiler/ - Ubuntu apt - libclosure-compiler-java-doc - 20130227+rhino-2: normalized package name match | Ubuntu 24.04 LTS package indexes: libclosure-compiler-java-doc from https://archive.ubuntu.com/ubuntu/dists/noble/universe/binary-amd64/Packages.gz | JavaScript optimizing compiler - Javadoc | https://developers.google.com/closure/compiler/ ## Related links - [Terminal utility packages](https://www.automicvault.com/pkg/terminal-utilities/) - Matched terminal and command-line workflow metadata. - [Text processing packages](https://www.automicvault.com/pkg/text-processing-tools/) - Matched text, document, or structured-data processing metadata. - [Developer build packages](https://www.automicvault.com/pkg/developer-build-tools/) - Matched build, compiler, generator, or developer workflow metadata. - [Language runtime packages](https://www.automicvault.com/pkg/language-runtime-packages/) - Matched language runtime, compiler, or interpreter metadata. - [openjdk](https://www.automicvault.com/pkg/brew/openjdk/) - Runtime dependency declared by Homebrew. - [emscripten](https://www.automicvault.com/pkg/brew/emscripten/) - Shares av.db curated category or tags: cli, compiler, developer-tools, javascript. - [lunarml](https://www.automicvault.com/pkg/brew/lunarml/) - Shares av.db curated category or tags: cli, compiler, developer-tools, javascript. - [ncc](https://www.automicvault.com/pkg/brew/ncc/) - Shares av.db curated category or tags: cli, compiler, developer-tools, javascript. - [swc](https://www.automicvault.com/pkg/brew/swc/) - Shares av.db curated category or tags: cli, compiler, developer-tools, javascript. - [bsc](https://www.automicvault.com/pkg/brew/bsc/) - Shares av.db curated category or tags: cli, compiler, developer-tools. - [cc65](https://www.automicvault.com/pkg/brew/cc65/) - Shares av.db curated category or tags: cli, compiler, developer-tools. - [grunt-cli](https://www.automicvault.com/pkg/brew/grunt-cli/) - Shares av.db curated category or tags: cli, developer-tools, javascript. - [lerna](https://www.automicvault.com/pkg/brew/lerna/) - Shares av.db curated category or tags: cli, developer-tools, javascript. - [gwt](https://www.automicvault.com/pkg/brew/gwt/) - Both packages touch the same language runtime or ecosystem. Shared terms: cli, compiler, developer, developer-tools, javascript. ## Combined YAML source View the package source record on GitHub. [combined/closure-compiler.yml](https://github.com/automic-vault/db/blob/main/combined/closure-compiler.yml) ## Sources - Nucleus package database - Geiger risk classifier - package-page enrichment - curated package history - package version freshness - av.db category and tag curation - package relationship graph - external package-manager database matches - cross-ecosystem install command graph