Closure Compiler

Closure Compiler is a JavaScript optimizing compiler. It parses your JavaScript, analyzes it, removes dead code and rewrites and minimizes what's left. It also checks syntax, variable references, and types, and warns about common JavaScript pitfalls. It is used in many of Google's JavaScript apps, including Gmail, Google Web Search, Google Maps, and Google Docs.

License	License The Apache Software License, Version 2.0
Categories	Categories JavaScript Languages Java Scala
GroupId	GroupId org.scala-js
ArtifactId	ArtifactId closure-compiler-java-6
Last Version	Last Version v20160517
Release Date	Release Date Jul 7, 2016
Type	Type jar
Description	Description Closure Compiler Closure Compiler is a JavaScript optimizing compiler. It parses your JavaScript, analyzes it, removes dead code and rewrites and minimizes what's left. It also checks syntax, variable references, and types, and warns about common JavaScript pitfalls. It is used in many of Google's JavaScript apps, including Gmail, Google Web Search, Google Maps, and Google Docs.
Project URL	Project URL https://github.com/scala-js/closure-compiler/
Project Organization	Project Organization Scala.js

Download closure-compiler-java-6

Filename	Size
closure-compiler-java-6-v20160517.pom
closure-compiler-java-6-v20160517.jar	6 MB
closure-compiler-java-6-v20160517-sources.jar	2 MB
closure-compiler-java-6-v20160517-javadoc.jar	3 MB
Browse

How to add to project

Apache Maven

<!-- https://jarcasting.com/artifacts/org.scala-js/closure-compiler-java-6/ -->
<dependency>
    <groupId>org.scala-js</groupId>
    <artifactId>closure-compiler-java-6</artifactId>
    <version>v20160517</version>
</dependency>

Gradle Groovy

// https://jarcasting.com/artifacts/org.scala-js/closure-compiler-java-6/
implementation 'org.scala-js:closure-compiler-java-6:v20160517'

Gradle Kotlin

// https://jarcasting.com/artifacts/org.scala-js/closure-compiler-java-6/
implementation ("org.scala-js:closure-compiler-java-6:v20160517")

Apache Buildr

'org.scala-js:closure-compiler-java-6:jar:v20160517'

Apache Ivy

<dependency org="org.scala-js" name="closure-compiler-java-6" rev="v20160517">
  <artifact name="closure-compiler-java-6" type="jar" />
</dependency>

Groovy Grape

@Grapes(
@Grab(group='org.scala-js', module='closure-compiler-java-6', version='v20160517')
)

Scala SBT

libraryDependencies += "org.scala-js" % "closure-compiler-java-6" % "v20160517"

Leiningen

[org.scala-js/closure-compiler-java-6 "v20160517"]

Dependencies

compile (6)

Group / Artifact	Type	Version
org.scala-js : closure-compiler-externs-java-6	jar	v20160517
args4j : args4j	jar	2.0.26
com.google.guava : guava	jar	19.0
com.google.protobuf : protobuf-java	jar	2.5.0
com.google.code.gson : gson	jar	2.2.4
com.google.code.findbugs : jsr305	jar	1.3.9

provided (1)

Group / Artifact	Type	Version
org.apache.ant : ant	jar	1.9.4

test (2)

Group / Artifact	Type	Version
com.google.truth : truth	jar	0.24
junit : junit	jar	4.11

Project Modules

There are no modules declared in this project.

Google Closure Compiler

The Closure Compiler is a tool for making JavaScript download and run faster. It is a true compiler for JavaScript. Instead of compiling from a source language to machine code, it compiles from JavaScript to better JavaScript. It parses your JavaScript, analyzes it, removes dead code and rewrites and minimizes what's left. It also checks syntax, variable references, and types, and warns about common JavaScript pitfalls.

Getting Started

Download the latest version (Release details here)
Download a specific version. Also available via:
- Maven
- NPM
See the Google Developers Site for documentation including instructions for running the compiler from the command line.

Options for Getting Help

Post in the Closure Compiler Discuss Group
Ask a question on Stack Overflow
Consult the FAQ

Building it Yourself

Note: The Closure Compiler requires Java 7 or higher.

Using Maven

Download Maven.

Add sonatype snapshots repository to ~/.m2/settings.xml:

<profile>
  <id>allow-snapshots</id>
     <activation><activeByDefault>true</activeByDefault></activation>
  <repositories>
    <repository>
      <id>snapshots-repo</id>
      <url>https://oss.sonatype.org/content/repositories/snapshots</url>
      <releases><enabled>false</enabled></releases>
      <snapshots><enabled>true</enabled></snapshots>
    </repository>
  </repositories>
</profile>

Run mvn -DskipTests (omit the -DskipTests if you want to run all the unit tests too).

This will produce a jar file called target/closure-compiler-1.0-SNAPSHOT.jar.

Using Eclipse

Download and open the Eclipse IDE.
Navigate to File > New > Project ... and create a Java Project. Give the project a name.
Select Create project from existing source and choose the root of the checked-out source tree as the existing directory.
Navigate to the build.xml file. You will see all the build rules in the Outline pane. Run the jar rule to build the compiler in build/compiler.jar.

Running

On the command line, at the root of this project, type

java -jar build/compiler.jar

This starts the compiler in interactive mode. Type

var x = 17 + 25;

then hit "Enter", then hit "Ctrl-Z" (on Windows) or "Ctrl-D" (on Mac or Linux) and "Enter" again. The Compiler will respond:

var x=42;

The Closure Compiler has many options for reading input from a file, writing output to a file, checking your code, and running optimizations. To learn more, type

java -jar compiler.jar --help

More detailed information about running the Closure Compiler is available in the documentation.

Compiling Multiple Scripts

If you have multiple scripts, you should compile them all together with one compile command.

java -jar compiler.jar --js_output_file=out.js in1.js in2.js in3.js ...

You can also use minimatch-style globs.

# Recursively include all js files in subdirs
java -jar compiler.jar --js_output_file=out.js 'src/**.js'

# Recursively include all js files in subdirs, excluding test files.
# Use single-quotes, so that bash doesn't try to expand the '!'
java -jar compiler.jar --js_output_file=out.js 'src/**.js' '!**_test.js'

The Closure Compiler will concatenate the files in the order they're passed at the command line.

If you're using globs or many files, you may start to run into problems with managing dependencies between scripts. In this case, you should use the Closure Library. It contains functions for enforcing dependencies between scripts, and Closure Compiler will re-order the inputs automatically.

How to Contribute

Reporting a bug

First make sure that it is really a bug and not simply the way that Closure Compiler works (especially true for ADVANCED_OPTIMIZATIONS).

Check the official documentation
Consult the FAQ
Search on Stack Overflow and in the Closure Compiler Discuss Group

If you still think you have found a bug, make sure someone hasn't already reported it. See the list of known issues.
If it hasn't been reported yet, post a new issue. Make sure to add enough detail so that the bug can be recreated. The smaller the reproduction code, the better.

Suggesting a Feature

Consult the FAQ to make sure that the behaviour you would like isn't specifically excluded (such as string inlining).
Make sure someone hasn't requested the same thing. See the list of known issues.
Read up on what type of feature requests are accepted.
Submit your request as an issue.

Submitting patches

All contributors must sign a contributor license agreement (CLA). A CLA basically says that you own the rights to any code you contribute, and that you give us permission to use that code in Closure Compiler. You maintain the copyright on that code. If you own all the rights to your code, you can fill out an individual CLA. If your employer has any rights to your code, then they also need to fill out a corporate CLA. If you don't know if your employer has any rights to your code, you should ask before signing anything. By default, anyone with an @google.com email address already has a CLA signed for them.
To make sure your changes are of the type that will be accepted, ask about your patch on the Closure Compiler Discuss Group
Fork the repository.
Make your changes.
Submit a pull request for your changes. A project developer will review your work and then merge your request into the project.