1 # [Google Closure Compiler](https://developers.google.com/closure/compiler/)
3 [![Build Status](https://travis-ci.org/google/closure-compiler.svg?branch=master)](https://travis-ci.org/google/closure-compiler)
5 The [Closure Compiler](https://developers.google.com/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.
8 * [Download the latest version](http://dl.google.com/closure-compiler/compiler-latest.zip) ([Release details here](https://github.com/google/closure-compiler/wiki/Releases))
9 * [Download a specific version](https://github.com/google/closure-compiler/wiki/Binary-Downloads)
10 * See the [Google Developers Site](https://developers.google.com/closure/compiler/docs/gettingstarted_app) for documentation including instructions for running the compiler from the command line.
12 ## Options for Getting Help
13 1. Post in the [Closure Compiler Discuss Group](https://groups.google.com/forum/#!forum/closure-compiler-discuss)
14 2. Ask a question on [Stack Overflow](http://stackoverflow.com/questions/tagged/google-closure-compiler)
15 3. Consult the [FAQ](https://github.com/google/closure-compiler/wiki/FAQ)
17 ## Building it Yourself
19 Note: The Closure Compiler requires [Java 7 or higher](http://www.java.com/).
21 ### Using [Ant](http://ant.apache.org/)
23 1. Download the [Ant build tool](http://ant.apache.org/bindownload.cgi).
25 2. At the root of the source tree, there is an Ant file named ```build.xml```.
26 To use it, navigate to the same directory and type the command
32 This will produce a jar file called ```build/compiler.jar```.
34 ### Using [Eclipse](http://www.eclipse.org/)
36 1. Download and open the [Eclipse IDE](http://www.eclipse.org/).
37 2. Navigate to ```File > New > Project ...``` and create a Java Project. Give
39 3. Select ```Create project from existing source``` and choose the root of the
40 checked-out source tree as the existing directory.
41 3. Navigate to the ```build.xml``` file. You will see all the build rules in
42 the Outline pane. Run the ```jar``` rule to build the compiler in
43 ```build/compiler.jar```.
47 On the command line, at the root of this project, type
50 java -jar build/compiler.jar
53 This starts the compiler in interactive mode. Type
59 then hit "Enter", then hit "Ctrl-Z" (on Windows) or "Ctrl-D" (on Mac or Linux)
60 and "Enter" again. The Compiler will respond:
66 The Closure Compiler has many options for reading input from a file, writing
67 output to a file, checking your code, and running optimizations. To learn more,
71 java -jar compiler.jar --help
74 More detailed information about running the Closure Compiler is available in the
75 [documentation](http://code.google.com/closure/compiler/docs/gettingstarted_app.html).
77 ## Compiling Multiple Scripts
79 If you have multiple scripts, you should compile them all together with one
83 java -jar compiler.jar --js_output_file=out.js in1.js in2.js in3.js ...
86 You can also use minimatch-style globs.
89 # Recursively include all js files in subdirs
90 java -jar compiler.jar --js_output_file=out.js 'src/**.js'
92 # Recursively include all js files in subdirs, exclusing test files.
93 # Use single-quotes, so that bash doesn't try to expand the '!'
94 java -jar compiler.jar --js_output_file=out.js 'src/**.js' '!**_test.js'
97 The Closure Compiler will concatenate the files in the order they're passed at
100 If you're using globs or many files, you may start to run into
101 problems with managing dependencies between scripts. In this case, you should
102 use the [Closure Library](https://developers.google.com/closure/library/). It
103 contains functions for enforcing dependencies between scripts, and Closure Compiler
104 will re-order the inputs automatically.
108 1. First make sure that it is really a bug and not simply the way that Closure Compiler works (especially true for ADVANCED_OPTIMIZATIONS).
109 * Check the [official documentation](https://developers.google.com/closure/compiler/)
110 * Consult the [FAQ](https://github.com/google/closure-compiler/wiki/FAQ)
111 * Search on [Stack Overflow](http://stackoverflow.com/questions/tagged/google-closure-compiler) and in the [Closure Compiler Discuss Group](https://groups.google.com/forum/#!forum/closure-compiler-discuss)
112 2. If you still think you have found a bug, make sure someone hasn't already reported it. See the list of [known issues](https://github.com/google/closure-compiler/issues).
113 3. 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.
115 ### Suggesting a Feature
116 1. Consult the [FAQ](https://github.com/google/closure-compiler/wiki/FAQ) to make sure that the behaviour you would like isn't specifically excluded (such as string inlining).
117 2. Make sure someone hasn't requested the same thing. See the list of [known issues](https://github.com/google/closure-compiler/issues).
118 3. Read up on [what type of feature requests are accepted](https://github.com/google/closure-compiler/wiki/FAQ#how-do-i-submit-a-feature-request-for-a-new-type-of-optimization).
119 4. Submit your reqest as an issue.
121 ### Submitting patches
122 1. All contributors must sign a contributor license agreement. See the [CONTRIBUTORS](https://raw.githubusercontent.com/google/closure-compiler/master/CONTRIBUTORS) file for details.
123 2. To make sure your changes are of the type that will be accepted, ask about your patch on the [Closure Compiler Discuss Group](https://groups.google.com/forum/#!forum/closure-compiler-discuss)
124 3. Fork the repository.
125 4. Make your changes.
126 5. Submit a pull request for your changes. A project developer will review your work and then merge your request into the project.
128 ## Closure Compiler License
130 Copyright 2009 The Closure Compiler Authors.
132 Licensed under the Apache License, Version 2.0 (the "License");
133 you may not use this file except in compliance with the License.
134 You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0.
136 Unless required by applicable law or agreed to in writing, software
137 distributed under the License is distributed on an "AS IS" BASIS,
138 WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
139 See the License for the specific language governing permissions and
140 limitations under the License.
142 ## Dependency Licenses
150 <code>src/com/google/javascript/rhino</code>, <code>test/com/google/javascript/rhino</code>
156 <td>http://www.mozilla.org/rhino</td>
161 <td>1.5R3, with heavy modifications</td>
166 <td>Netscape Public License and MPL / GPL dual license</td>
171 <td>A partial copy of Mozilla Rhino. Mozilla Rhino is an
172 implementation of JavaScript for the JVM. The JavaScript
173 parse tree data structures were extracted and modified
174 significantly for use by Google's JavaScript compiler.</td>
178 <td>Local Modifications</td>
179 <td>The packages have been renamespaced. All code not
180 relevant to the parse tree has been removed. A JsDoc parser and static typing
181 system have been added.</td>
190 <td><code>lib/args4j.jar</code></td>
195 <td>https://args4j.dev.java.net/</td>
210 <td>args4j is a small Java class library that makes it easy to parse command line
211 options/arguments in your CUI application.</td>
215 <td>Local Modifications</td>
225 <td><code>lib/guava.jar</code></td>
230 <td>https://github.com/google/guava</td>
240 <td>Apache License 2.0</td>
245 <td>Google's core Java libraries.</td>
249 <td>Local Modifications</td>
259 <td><code>lib/jsr305.jar</code></td>
264 <td>http://code.google.com/p/jsr-305/</td>
269 <td>svn revision 47</td>
279 <td>Annotations for software defect detection.</td>
283 <td>Local Modifications</td>
293 <td><code>lib/junit.jar</code></td>
298 <td>http://sourceforge.net/projects/junit/</td>
308 <td>Common Public License 1.0</td>
313 <td>A framework for writing and running automated tests in Java.</td>
317 <td>Local Modifications</td>
327 <td><code>lib/protobuf-java.jar</code></td>
332 <td>http://code.google.com/p/protobuf/</td>
342 <td>New BSD License</td>
347 <td>Supporting libraries for protocol buffers,
348 an encoding of structured data.</td>
352 <td>Local Modifications</td>
362 <td><code>lib/truth.jar</code></td>
367 <td>https://github.com/google/truth</td>
377 <td>Apache License 2.0</td>
382 <td>Assertion/Proposition framework for Java unit tests</td>
386 <td>Local Modifications</td>
397 <code>lib/ant.jar</code>, <code>lib/ant-launcher.jar</code>
403 <td>http://ant.apache.org/bindownload.cgi</td>
413 <td>Apache License 2.0</td>
418 <td>Ant is a Java based build tool. In theory it is kind of like "make"
419 without make's wrinkles and with the full portability of pure java code.</td>
423 <td>Local Modifications</td>
433 <td><code>lib/gson.jar</code></td>
438 <td>https://code.google.com/p/google-gson/</td>
448 <td>Apache license 2.0</td>
453 <td>A Java library to convert JSON to Java objects and vice-versa</td>
457 <td>Local Modifications</td>
462 ### Node.js Closure Compiler Externs
467 <td><code>contrib/nodejs</code></td>
472 <td>https://github.com/dcodeIO/node.js-closure-compiler-externs</td>
477 <td>e891b4fbcf5f466cc4307b0fa842a7d8163a073a</td>
482 <td>Apache 2.0 license</td>
487 <td>Type contracts for NodeJS APIs</td>
491 <td>Local Modifications</td>
492 <td>Substantial changes to make them compatible with NpmCommandLineRunner.</td>