{"id":13470333,"url":"https://github.com/google/closure-compiler","last_synced_at":"2025-09-09T20:58:52.294Z","repository":{"id":16100098,"uuid":"18845024","full_name":"google/closure-compiler","owner":"google","description":"A JavaScript checker and optimizer.","archived":false,"fork":false,"pushed_at":"2025-04-30T20:02:30.000Z","size":186627,"stargazers_count":7501,"open_issues_count":913,"forks_count":1163,"subscribers_count":232,"default_branch":"master","last_synced_at":"2025-04-30T20:22:52.885Z","etag":null,"topics":["closure-compiler","javascript","optimization","typechecking"],"latest_commit_sha":null,"homepage":"https://developers.google.com/closure/compiler/","language":"Java","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":"apache-2.0","status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/google.png","metadata":{"files":{"readme":"README.md","changelog":null,"contributing":null,"funding":null,"license":"LICENSE","code_of_conduct":"code_of_conduct.md","threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":null,"support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null,"zenodo":null}},"created_at":"2014-04-16T15:30:36.000Z","updated_at":"2025-04-30T20:02:35.000Z","dependencies_parsed_at":"2023-02-13T05:30:47.364Z","dependency_job_id":"d5ff848a-cc2c-446e-a2a6-6da8104f8820","html_url":"https://github.com/google/closure-compiler","commit_stats":{"total_commits":18943,"total_committers":1113,"mean_commits":"17.019766397124886","dds":0.8450615002903448,"last_synced_commit":"096e4cf4783f8178224eb0192d0e9e286bc69535"},"previous_names":[],"tags_count":208,"template":false,"template_full_name":null,"repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/google%2Fclosure-compiler","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/google%2Fclosure-compiler/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/google%2Fclosure-compiler/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/google%2Fclosure-compiler/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/google","download_url":"https://codeload.github.com/google/closure-compiler/tar.gz/refs/heads/master","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":252525308,"owners_count":21762267,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["closure-compiler","javascript","optimization","typechecking"],"created_at":"2024-07-31T16:00:28.596Z","updated_at":"2025-09-09T20:58:52.264Z","avatar_url":"https://github.com/google.png","language":"Java","readme":"# [Google Closure Compiler](https://developers.google.com/closure/compiler/)\n\n[![OpenSSF Scorecard](https://api.securityscorecards.dev/projects/github.com/google/closure-compiler/badge)](https://api.securityscorecards.dev/projects/github.com/google/closure-compiler)\n[![Build Status](https://github.com/google/closure-compiler/workflows/Compiler%20CI/badge.svg)](https://github.com/google/closure-compiler/actions)\n[![Open Source Helpers](https://www.codetriage.com/google/closure-compiler/badges/users.svg)](https://www.codetriage.com/google/closure-compiler)\n[![Contributor Covenant](https://img.shields.io/badge/Contributor%20Covenant-v2.0%20adopted-ff69b4.svg)](https://github.com/google/closure-compiler/blob/master/code_of_conduct.md)\n\nThe [Closure Compiler](https://developers.google.com/closure/compiler/) is a\ntool for making JavaScript download and run faster. It is a true compiler for\nJavaScript. Instead of compiling from a source language to machine code, it\ncompiles from JavaScript to better JavaScript. It parses your JavaScript,\nanalyzes it, removes dead code and rewrites and minimizes what's left. It also\nchecks syntax, variable references, and types, and warns about common JavaScript\npitfalls.\n\n## Important Caveats\n\n1. Compilation modes other than `ADVANCED` were always an afterthought and we\n   have deprecated those modes. We believe that other tools perform comparably\n   for non-`ADVANCED` modes and are better integrated into the broader JS\n   ecosystem.\n\n1. Closure Compiler is not suitable for arbitrary JavaScript.  For `ADVANCED`\n   mode to generate working JavaScript, the input JS code must be written with\n   closure-compiler in mind.\n\n1. Closure Compiler is a \"whole world\" optimizer. It expects to directly see or\n   at least receive information about every possible use of every global or\n   exported variable and every property name.\n\n   It will aggressively remove and rename variables and properties in order to\n   make the output code as small as possible. This will result in broken output\n   JS, if uses of global variables or properties are hidden from it.\n\n    Although one can write custom externs files to tell the compiler to leave\n    some names unchanged so they can safely be accessed by code that is not part\n    of the compilation, this is often tedious to maintain.\n\n1. Closure Compiler property renaming requires you to consistently access a\n   property with either `obj[p]` or `obj.propName`, but not both.\n\n   When you access a property with square brackets (e.g. `obj[p]`) or using some\n   other indirect method like `let {p} = obj;` this hides the literal name of\n   the property being referenced from the compiler. It cannot know if\n   `obj.propName` is referring to the same property as `obj[p]`. In some cases\n   it will notice this problem and stop the compilation with an error. In other\n   cases it will rename `propName` to something shorter, without noticing this\n   problem, resulting in broken output JS code.\n\n1. Closure Compiler aggressively inlines global variables and flattens chains\n   of property names on global variables (e.g. `myFoo.some.sub.property` -\u003e\n   `myFoo$some$sub$property`), to make reasoning about them easier for detecting\n   unused code.\n\n   It tries to either back off from doing this or halt with an error when\n   doing it will generate broken JS output, but there are cases where it will\n   fail to recognize the problem and simply generate broken JS without warning.\n   This is much more likely to happen in code that was not explicitly written\n   with Closure Compiler in mind.\n\n1. Closure compiler and the externs it uses by default assume that the target\n   environment is a web browser window.\n\n   WebWorkers are supported also, but the compiler will likely fail to warn\n   you if you try to use features that aren't actually available to a WebWorker.\n\n   Some externs files and features have been added to Closure Compiler to\n   support the NodeJS environment, but they are not actively supported and\n   never worked very well.\n\n1. JavaScript that does not use the `goog.module()` and `goog.require()` from\n   `base.js` to declare and use modules is not well supported.\n\n    The ECMAScript `import` and `export` syntax did not exist until 2015.\n    Closure compiler and `closure-library` developed their own means for\n    declaring and using modules, and this remains the only well supported\n    way of defining modules.\n\n    The compiler does implement some understanding of ECMAScript modules,\n    but changing Google's projects to use the newer syntax has never offered\n    a benefit that was worth the cost of the change. Google's TypeScript code\n    uses ECMAScript modules, but they are converted to `goog.module()` syntax\n    before closure-compiler sees them. So, effectively the ECMAScript modules\n    support is unused within Google. This means we are unlikely to notice\n    or fix bugs in the support for ECMAScript modules.\n\n    Support for CommonJS modules as input was added in the past, but is not\n    used within Google, and is likely to be entirely removed sometime in 2024.\n\n## Supported uses\n\nClosure Compiler is used by Google projects to:\n\n*   Drastically reduce the code size of very large JavaScript applications\n\n*   Check the JS code for errors and for conformance to general and/or\n    project-specific best practices.\n\n*   Define user-visible messages in a way that makes it possible to replace\n    them with translated versions to create localized versions of an\n    application.\n\n*   Transpile newer JS features into a form that will run on browsers that\n    lack support for those features.\n\n*   Break the output application into chunks that may be individually loaded\n    as needed.\n\n    NOTE: These chunks are plain JavaScript scripts. They do not use the\n    ECMAScript `import` and `export` syntax.\n\nTo achieve these goals closure compiler places many restrictions on its input:\n\n*   Use `goog.module()` and `goog.require()` to declare and use modules.\n\n    Support for the `import` and `export` syntax added in ES6 is not actively\n    maintained.\n\n*   Use annotations in comments to declare type information and provide\n    information the compiler needs to avoid breaking some code patterns\n    (e.g. `@nocollapse` and `@noinline`).\n\n*   Either use only dot-access (e.g. `object.property`) or only use dynamic\n    access (e.g. `object[propertyName]` or `Object.keys(object)`) to access\n    the properties of a particular object type.\n\n    Mixing these will hide some uses of a property from the compiler, resulting\n    in broken output code when it renames the property.\n\n*   In general the compiler expects to see an entire application as a single\n    compilation. Interfaces must be carefully and explicitly constructed in\n    order to allow interoperation with code outside of the compilation unit.\n\n    The compiler assumes it can see all uses of all variables and properties\n    and will freely rename them or remove them if they appear unused.\n\n*   Use externs files to inform the compiler of any variables or properties\n    that it must not remove or rename.\n\n    There are default externs files declaring the standard JS and DOM global\n    APIs. More externs files are necessary if you are using less common\n    APIs or expect some external JavaScript code to access an API in the\n    code you are compiling.\n\n## Getting Started\n\nThe easiest way to install the compiler is with [NPM](https://npmjs.com) or\n[Yarn](https://yarnpkg.com):\n\n```bash\nyarn global add google-closure-compiler\n# OR\nnpm i -g google-closure-compiler\n```\n\nThe package manager will link the binary for you, and you can access the\ncompiler with:\n\n```bash\ngoogle-closure-compiler\n```\n\nThis starts the compiler in interactive mode. Type:\n\n```javascript\nvar x = 17 + 25;\n```\n\nHit `Enter`, then `Ctrl+Z` (on Windows) or `Ctrl+D` (on Mac/Linux), then `Enter`\nagain. The Compiler will respond with the compiled output (using `SIMPLE` mode\nby default):\n\n```javascript\nvar x=42;\n```\n\n#### Downloading from Maven Repository\n\nA pre-compiled release of the compiler is also available via\n[Maven](https://mvnrepository.com/artifact/com.google.javascript/closure-compiler).\n\n### Web-based tooling\n\nhttps://jscompressor.treblereel.dev/ is a web-based UI and REST API for Closure\nCompiler, developed and maintained by at\nhttps://github.com/treblereel/jscompressor.\n\n### Basic usage\n\nThe Closure Compiler has many options for reading input from a file, writing\noutput to a file, checking your code, and running optimizations. Here is a\nsimple example of compressing a JS program:\n\n```bash\ngoogle-closure-compiler --js file.js --js_output_file file.out.js\n```\n\nWe get the **most benefit** from the compiler if we give it **all of our source\ncode** (see [Compiling Multiple Scripts](#compiling-multiple-scripts)), which\nallows us to use `ADVANCED` optimizations:\n\n```bash\ngoogle-closure-compiler -O ADVANCED rollup.js --js_output_file rollup.min.js\n```\n\nNOTE: The output below is just an example and not kept up-to-date. The\n  [Flags and Options wiki page](https://github.com/google/closure-compiler/wiki/Flags-and-Options)\n  is updated during each release.\n\nTo see all of the compiler's options, type:\n\n```bash\ngoogle-closure-compiler --help\n```\n\n\u003ctable\u003e\n\u003cthead\u003e\n  \u003ctr\u003e\n    \u003cth\u003e\u003ccode\u003e--flag\u003c/code\u003e\u003c/th\u003e\n    \u003cth\u003eDescription\u003c/th\u003e\n  \u003c/tr\u003e\n\u003c/thead\u003e\n\u003ctbody\u003e\n  \u003ctr\u003e\n    \u003ctd\u003e\u003ccode\u003e--compilation_level (-O)\u003c/code\u003e\u003c/td\u003e\n    \u003ctd\u003e\n      Specifies the compilation level to use.\n      Options: \u003ccode\u003eBUNDLE\u003c/code\u003e, \u003ccode\u003eWHITESPACE_ONLY\u003c/code\u003e,\n      \u003ccode\u003eSIMPLE\u003c/code\u003e (default), \u003ccode\u003eADVANCED\u003c/code\u003e\n    \u003c/td\u003e\n  \u003c/tr\u003e\n  \u003ctr\u003e\n    \u003ctd\u003e\u003ccode\u003e--env\u003c/code\u003e\u003c/td\u003e\n    \u003ctd\u003e\n      Determines the set of builtin externs to load.\n      Options: \u003ccode\u003eBROWSER\u003c/code\u003e, \u003ccode\u003eCUSTOM\u003c/code\u003e.\n      Defaults to \u003ccode\u003eBROWSER\u003c/code\u003e.\n    \u003c/td\u003e\n  \u003c/tr\u003e\n  \u003ctr\u003e\n    \u003ctd\u003e\u003ccode\u003e--externs\u003c/code\u003e\u003c/td\u003e\n    \u003ctd\u003eThe file containing JavaScript externs. You may specify multiple\u003c/td\u003e\n  \u003c/tr\u003e\n  \u003ctr\u003e\n    \u003ctd\u003e\u003ccode\u003e--js\u003c/code\u003e\u003c/td\u003e\n    \u003ctd\u003e\n      The JavaScript filename. You may specify multiple. The flag name is\n      optional, because args are interpreted as files by default. You may also\n      use minimatch-style glob patterns. For example, use\n      \u003ccode\u003e--js='**.js' --js='!**_test.js'\u003c/code\u003e to recursively include all\n      js files that do not end in \u003ccode\u003e_test.js\u003c/code\u003e\n    \u003c/td\u003e\n  \u003c/tr\u003e\n  \u003ctr\u003e\n    \u003ctd\u003e\u003ccode\u003e--js_output_file\u003c/code\u003e\u003c/td\u003e\n    \u003ctd\u003e\n      Primary output filename. If not specified, output is written to stdout.\n    \u003c/td\u003e\n  \u003c/tr\u003e\n  \u003ctr\u003e\n    \u003ctd\u003e\u003ccode\u003e--language_in\u003c/code\u003e\u003c/td\u003e\n    \u003ctd\u003e\n      Sets the language spec to which input sources should conform.\n      Options: \u003ccode\u003eECMASCRIPT3\u003c/code\u003e, \u003ccode\u003eECMASCRIPT5\u003c/code\u003e,\n      \u003ccode\u003eECMASCRIPT5_STRICT\u003c/code\u003e, \u003ccode\u003eECMASCRIPT_2015\u003c/code\u003e,\n      \u003ccode\u003eECMASCRIPT_2016\u003c/code\u003e, \u003ccode\u003eECMASCRIPT_2017\u003c/code\u003e,\n      \u003ccode\u003eECMASCRIPT_2018\u003c/code\u003e, \u003ccode\u003eECMASCRIPT_2019\u003c/code\u003e,\n      \u003ccode\u003eSTABLE\u003c/code\u003e, \u003ccode\u003eECMASCRIPT_NEXT\u003c/code\u003e\n    \u003c/td\u003e\n  \u003c/tr\u003e\n  \u003ctr\u003e\n    \u003ctd\u003e\u003ccode\u003e--language_out\u003c/code\u003e\u003c/td\u003e\n    \u003ctd\u003e\n      Sets the language spec to which output should conform.\n      Options: \u003ccode\u003eECMASCRIPT3\u003c/code\u003e, \u003ccode\u003eECMASCRIPT5\u003c/code\u003e,\n      \u003ccode\u003eECMASCRIPT5_STRICT\u003c/code\u003e, \u003ccode\u003eECMASCRIPT_2015\u003c/code\u003e,\n      \u003ccode\u003eECMASCRIPT_2016\u003c/code\u003e, \u003ccode\u003eECMASCRIPT_2017\u003c/code\u003e,\n      \u003ccode\u003eECMASCRIPT_2018\u003c/code\u003e, \u003ccode\u003eECMASCRIPT_2019\u003c/code\u003e,\n      \u003ccode\u003eSTABLE\u003c/code\u003e\n    \u003c/td\u003e\n  \u003c/tr\u003e\n  \u003ctr\u003e\n    \u003ctd\u003e\u003ccode\u003e--warning_level (-W)\u003c/code\u003e\u003c/td\u003e\n    \u003ctd\u003eSpecifies the warning level to use.\n      Options: \u003ccode\u003eQUIET\u003c/code\u003e, \u003ccode\u003eDEFAULT\u003c/code\u003e, \u003ccode\u003eVERBOSE\u003c/code\u003e\n    \u003c/td\u003e\n  \u003c/tr\u003e\n\u003c/tbody\u003e\n\u003c/table\u003e\n\n#### 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.\n\n### NodeJS API\n\nYou can access the compiler in a JS program by importing\n`google-closure-compiler`:\n\n```javascript\nimport closureCompiler from 'google-closure-compiler';\nconst { compiler } = closureCompiler;\n\nnew compiler({\n  js: 'file-one.js',\n  compilation_level: 'ADVANCED'\n});\n```\n\nThis package will provide programmatic access to the native Graal binary in most\ncases, and will fall back to the Java version otherwise.\n\n#### Please see the [closure-compiler-npm](https://github.com/google/closure-compiler-npm/tree/master/packages/google-closure-compiler) repository for documentation on accessing the compiler in JS.\n\n## Compiling Multiple Scripts\n\nIf you have multiple scripts, you should compile them all together with one\ncompile command.\n\n```bash\ngoogle-closure-compiler in1.js in2.js in3.js --js_output_file out.js\n```\n\nYou can also use minimatch-style globs.\n\n```bash\n# Recursively include all js files in subdirs\ngoogle-closure-compiler 'src/**.js' --js_output_file out.js\n\n# Recursively include all js files in subdirs, excluding test files.\n# Use single-quotes, so that bash doesn't try to expand the '!'\ngoogle-closure-compiler 'src/**.js' '!**_test.js' --js_output_file out.js\n```\n\nThe Closure Compiler will concatenate the files in the order they're passed at\nthe command line.\n\nIf you're using globs or many files, you may start to run into problems with\nmanaging dependencies between scripts. In this case, you should use the\nincluded [lib/base.js](lib/base.js) that provides functions for enforcing\ndependencies between scripts (namely `goog.module` and `goog.require`). Closure\nCompiler will re-order the inputs automatically.\n\n## Closure JavaScript Library\n\nThe Closure Compiler releases with [lib/base.js](lib/base.js) that provides\nJavaScript functions and variables that serve as primitives enabling certain\nfeatures of the Closure Compiler. This file is a derivative of the\n[identically named base.js](https://github.com/google/closure-library/blob/7818ff7dc0b53555a7fb3c3427e6761e88bde3a2/closure/goog/base.js)\nin the\n[soon-to-be deprecated](https://github.com/google/closure-library/issues/1214)\nClosure Library. This `base.js` will be supported by Closure Compiler going\nforward and may receive new features. It was designed to only retain its\nperceived core parts.\n\n## Getting Help\n\n1.  Post in the\n    [Closure Compiler Discuss Group](https://groups.google.com/forum/#!forum/closure-compiler-discuss).\n2.  Ask a question on\n    [Stack Overflow](https://stackoverflow.com/questions/tagged/google-closure-compiler).\n3.  Consult the [FAQ](https://github.com/google/closure-compiler/wiki/FAQ).\n\n## Building the Compiler\n\nTo build the compiler yourself, you will need the following:\n\nPrerequisite                                                               | Description\n-------------------------------------------------------------------------- | -----------\n[Java 21 or later](https://java.com)                                       | Used to compile the compiler's source code.\n[NodeJS](https://nodejs.org)                                               | Used to generate resources used by Java compilation\n[Git](https://git-scm.com/)                                                | Used by Bazel to download dependencies.\n[Bazelisk](https://bazel.build/install/bazelisk) | Used to build the various compiler targets.\n\n### Installing Bazelisk\n\nBazelisk is a wrapper around Bazel that dynamically loads the appropriate\nversion of Bazel for a given repository. Using it prevents spurious errors that\nresult from using the wrong version of Bazel to build the compiler, as well as\nmakes it easy to use different Bazel versions for other projects.\n\nBazelisk is available through many package managers. Feel free to use whichever\nyou're most comfortable with.\n\n[Instructions for installing Bazelisk](https://bazel.build/install/bazelisk).\n\n### Building from a terminal\n\n```bash\n$ bazelisk build //:compiler_uberjar_deploy.jar\n# OR to build everything\n$ bazelisk build //:all\n```\n\n### Testing from a terminal\n\nTests can be executed in a similar way. The following command will run all tests\nin the repo.\n\n```bash\n$ bazelisk test //:all\n```\n\nThere are hundreds of individual test targets, so it will take a few\nminutes to run all of them. While developing, it's usually better to specify\nthe exact tests you're interested in.\n\n```bash\nbazelisk test //:$path_to_test_file\n```\n\n### Building from an IDE\n\nSee [Bazel IDE Integrations](https://docs.bazel.build/versions/master/ide.html).\n\n### Running\n\nOnce the compiler has been built, the compiled JAR will be in the `bazel-bin/`\ndirectory. You can access it with a call to `java -jar ...` or by using the\npackage.json script:\n\n```bash\n# java -jar bazel-bin/compiler_uberjar_deploy.jar [...args]\nyarn compile [...args]\n```\n\n#### Running using Eclipse\n\n1.  Open the class `src/com/google/javascript/jscomp/CommandLineRunner.java` or\n    create your own extended version of the class.\n2.  Run the class in Eclipse.\n3.  See the instructions above on how to use the interactive mode - but beware\n    of the\n    [bug](https://stackoverflow.com/questions/4711098/passing-end-of-transmission-ctrl-d-character-in-eclipse-cdt-console)\n    regarding passing \"End of Transmission\" in the Eclipse console.\n\n## Contributing\n\n### Contributor code of conduct\n\nHowever you choose to contribute, please abide by our\n[code of conduct](https://github.com/google/closure-compiler/blob/master/code_of_conduct.md) to\nkeep our community a healthy and welcoming place.\n\n### Reporting a bug\n\n1.  First make sure that it is really a bug and not simply the way that Closure\n    Compiler works (especially true for ADVANCED_OPTIMIZATIONS).\n    *   Check the\n        [official documentation](https://developers.google.com/closure/compiler/)\n    *   Consult the [FAQ](https://github.com/google/closure-compiler/wiki/FAQ)\n    *   Search on\n        [Stack Overflow](https://stackoverflow.com/questions/tagged/google-closure-compiler)\n        and in the\n        [Closure Compiler Discuss Group](https://groups.google.com/forum/#!forum/closure-compiler-discuss)\n    *   Look through the list of\n        [compiler assumptions](https://github.com/google/closure-compiler/wiki/Compiler-Assumptions).\n2.  If you still think you have found a bug, make sure someone hasn't already\n    reported it. See the list of\n    [known issues](https://github.com/google/closure-compiler/issues).\n3.  If it hasn't been reported yet, post a new issue. Make sure to add enough\n    detail so that the bug can be recreated. The smaller the reproduction code,\n    the better.\n\n### Suggesting a feature\n\n1.  Consult the [FAQ](https://github.com/google/closure-compiler/wiki/FAQ) to\n    make sure that the behaviour you would like isn't specifically excluded\n    (such as string inlining).\n2.  Make sure someone hasn't requested the same thing. See the list of\n    [known issues](https://github.com/google/closure-compiler/issues).\n3.  Read up on\n    [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).\n4.  Submit your request as an issue.\n\n### Submitting patches\n\n1.  All contributors must sign a contributor license agreement (CLA). A CLA\n    basically says that you own the rights to any code you contribute, and that\n    you give us permission to use that code in Closure Compiler. You maintain\n    the copyright on that code. If you own all the rights to your code, you can\n    fill out an\n    [individual CLA](https://code.google.com/legal/individual-cla-v1.0.html). If\n    your employer has any rights to your code, then they also need to fill out a\n    [corporate CLA](https://code.google.com/legal/corporate-cla-v1.0.html). If\n    you don't know if your employer has any rights to your code, you should ask\n    before signing anything. By default, anyone with an @google.com email\n    address already has a CLA signed for them.\n2.  To make sure your changes are of the type that will be accepted, ask about\n    your patch on the\n    [Closure Compiler Discuss Group](https://groups.google.com/forum/#!forum/closure-compiler-discuss)\n3.  Fork the repository.\n4.  Make your changes. Check out our\n    [coding conventions](https://github.com/google/closure-compiler/wiki/Contributors#coding-conventions)\n    for details on making sure your code is in correct style.\n5.  Submit a pull request for your changes. A project developer will review your\n    work and then merge your request into the project.\n\n## Closure Compiler License\n\nCopyright 2009 The Closure Compiler Authors.\n\nLicensed under the Apache License, Version 2.0 (the \"License\"); you may not use\nthis file except in compliance with the License. You may obtain a copy of the\nLicense at http://www.apache.org/licenses/LICENSE-2.0.\n\nUnless required by applicable law or agreed to in writing, software distributed\nunder the License is distributed on an \"AS IS\" BASIS, WITHOUT WARRANTIES OR\nCONDITIONS OF ANY KIND, either express or implied. See the License for the\nspecific language governing permissions and limitations under the License.\n\n## Dependency Licenses\n\n### Rhino\n\n\u003ctable\u003e\n  \u003ctr\u003e\n    \u003ctd\u003eCode Path\u003c/td\u003e\n    \u003ctd\u003e\n      \u003ccode\u003esrc/com/google/javascript/rhino\u003c/code\u003e, \u003ccode\u003etest/com/google/javascript/rhino\u003c/code\u003e\n    \u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eURL\u003c/td\u003e\n    \u003ctd\u003ehttps://developer.mozilla.org/en-US/docs/Mozilla/Projects/Rhino\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eVersion\u003c/td\u003e\n    \u003ctd\u003e1.5R3, with heavy modifications\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eLicense\u003c/td\u003e\n    \u003ctd\u003eNetscape Public License and MPL / GPL dual license\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eDescription\u003c/td\u003e\n    \u003ctd\u003eA partial copy of Mozilla Rhino. Mozilla Rhino is an\nimplementation of JavaScript for the JVM.  The JavaScript parse tree data\nstructures were extracted and modified significantly for use by Google's\nJavaScript compiler.\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eLocal Modifications\u003c/td\u003e\n    \u003ctd\u003eThe packages have been renamespaced. All code not\nrelevant to the parse tree has been removed. A JsDoc parser and static typing\nsystem have been added.\u003c/td\u003e\n  \u003c/tr\u003e\n\u003c/table\u003e\n\n### Args4j\n\n\u003ctable\u003e\n  \u003ctr\u003e\n    \u003ctd\u003eURL\u003c/td\u003e\n    \u003ctd\u003ehttp://args4j.kohsuke.org/\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eVersion\u003c/td\u003e\n    \u003ctd\u003e2.33\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eLicense\u003c/td\u003e\n    \u003ctd\u003eMIT\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eDescription\u003c/td\u003e\n    \u003ctd\u003eargs4j is a small Java class library that makes it easy to parse command line\noptions/arguments in your CUI application.\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eLocal Modifications\u003c/td\u003e\n    \u003ctd\u003eNone\u003c/td\u003e\n  \u003c/tr\u003e\n\u003c/table\u003e\n\n### Guava Libraries\n\n\u003ctable\u003e\n  \u003ctr\u003e\n    \u003ctd\u003eURL\u003c/td\u003e\n    \u003ctd\u003ehttps://github.com/google/guava\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eVersion\u003c/td\u003e\n    \u003ctd\u003e31.0.1\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eLicense\u003c/td\u003e\n    \u003ctd\u003eApache License 2.0\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eDescription\u003c/td\u003e\n    \u003ctd\u003eGoogle's core Java libraries.\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eLocal Modifications\u003c/td\u003e\n    \u003ctd\u003eNone\u003c/td\u003e\n  \u003c/tr\u003e\n\u003c/table\u003e\n\n### JSR 305\n\n\u003ctable\u003e\n  \u003ctr\u003e\n    \u003ctd\u003eURL\u003c/td\u003e\n    \u003ctd\u003ehttps://github.com/findbugsproject/findbugs\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eVersion\u003c/td\u003e\n    \u003ctd\u003e3.0.1\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eLicense\u003c/td\u003e\n    \u003ctd\u003eBSD License\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eDescription\u003c/td\u003e\n    \u003ctd\u003eAnnotations for software defect detection.\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eLocal Modifications\u003c/td\u003e\n    \u003ctd\u003eNone\u003c/td\u003e\n  \u003c/tr\u003e\n\u003c/table\u003e\n\n### JUnit\n\n\u003ctable\u003e\n  \u003ctr\u003e\n    \u003ctd\u003eURL\u003c/td\u003e\n    \u003ctd\u003ehttp://junit.org/junit4/\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eVersion\u003c/td\u003e\n    \u003ctd\u003e4.13\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eLicense\u003c/td\u003e\n    \u003ctd\u003eCommon Public License 1.0\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eDescription\u003c/td\u003e\n    \u003ctd\u003eA framework for writing and running automated tests in Java.\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eLocal Modifications\u003c/td\u003e\n    \u003ctd\u003eNone\u003c/td\u003e\n  \u003c/tr\u003e\n\u003c/table\u003e\n\n### Protocol Buffers\n\n\u003ctable\u003e\n  \u003ctr\u003e\n    \u003ctd\u003eURL\u003c/td\u003e\n    \u003ctd\u003ehttps://github.com/google/protobuf\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eVersion\u003c/td\u003e\n    \u003ctd\u003e3.0.2\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eLicense\u003c/td\u003e\n    \u003ctd\u003eNew BSD License\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eDescription\u003c/td\u003e\n    \u003ctd\u003eSupporting libraries for protocol buffers,\nan encoding of structured data.\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eLocal Modifications\u003c/td\u003e\n    \u003ctd\u003eNone\u003c/td\u003e\n  \u003c/tr\u003e\n\u003c/table\u003e\n\n### RE2/J\n\n\u003ctable\u003e\n  \u003ctr\u003e\n    \u003ctd\u003eURL\u003c/td\u003e\n    \u003ctd\u003ehttps://github.com/google/re2j\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eVersion\u003c/td\u003e\n    \u003ctd\u003e1.3\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eLicense\u003c/td\u003e\n    \u003ctd\u003eNew BSD License\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eDescription\u003c/td\u003e\n    \u003ctd\u003eLinear time regular expression matching in Java.\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eLocal Modifications\u003c/td\u003e\n    \u003ctd\u003eNone\u003c/td\u003e\n  \u003c/tr\u003e\n\u003c/table\u003e\n\n### Truth\n\n\u003ctable\u003e\n  \u003ctr\u003e\n    \u003ctd\u003eURL\u003c/td\u003e\n    \u003ctd\u003ehttps://github.com/google/truth\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eVersion\u003c/td\u003e\n    \u003ctd\u003e1.1\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eLicense\u003c/td\u003e\n    \u003ctd\u003eApache License 2.0\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eDescription\u003c/td\u003e\n    \u003ctd\u003eAssertion/Proposition framework for Java unit tests\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eLocal Modifications\u003c/td\u003e\n    \u003ctd\u003eNone\u003c/td\u003e\n  \u003c/tr\u003e\n\u003c/table\u003e\n\n### Ant\n\n\u003ctable\u003e\n  \u003ctr\u003e\n    \u003ctd\u003eURL\u003c/td\u003e\n    \u003ctd\u003ehttps://ant.apache.org/bindownload.cgi\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eVersion\u003c/td\u003e\n    \u003ctd\u003e1.10.11\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eLicense\u003c/td\u003e\n    \u003ctd\u003eApache License 2.0\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eDescription\u003c/td\u003e\n    \u003ctd\u003eAnt is a Java based build tool. In theory it is kind of like \"make\"\nwithout make's wrinkles and with the full portability of pure java code.\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eLocal Modifications\u003c/td\u003e\n    \u003ctd\u003eNone\u003c/td\u003e\n  \u003c/tr\u003e\n\u003c/table\u003e\n\n### GSON\n\n\u003ctable\u003e\n  \u003ctr\u003e\n    \u003ctd\u003eURL\u003c/td\u003e\n    \u003ctd\u003ehttps://github.com/google/gson\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eVersion\u003c/td\u003e\n    \u003ctd\u003e2.9.1\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eLicense\u003c/td\u003e\n    \u003ctd\u003eApache license 2.0\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eDescription\u003c/td\u003e\n    \u003ctd\u003eA Java library to convert JSON to Java objects and vice-versa\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eLocal Modifications\u003c/td\u003e\n    \u003ctd\u003eNone\u003c/td\u003e\n  \u003c/tr\u003e\n\u003c/table\u003e\n\n### Node.js Closure Compiler Externs\n\n\u003ctable\u003e\n  \u003ctr\u003e\n    \u003ctd\u003eCode Path\u003c/td\u003e\n    \u003ctd\u003e\u003ccode\u003econtrib/nodejs\u003c/code\u003e\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eURL\u003c/td\u003e\n    \u003ctd\u003ehttps://github.com/dcodeIO/node.js-closure-compiler-externs\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eVersion\u003c/td\u003e\n    \u003ctd\u003ee891b4fbcf5f466cc4307b0fa842a7d8163a073a\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eLicense\u003c/td\u003e\n    \u003ctd\u003eApache 2.0 license\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eDescription\u003c/td\u003e\n    \u003ctd\u003eType contracts for NodeJS APIs\u003c/td\u003e\n  \u003c/tr\u003e\n\n  \u003ctr\u003e\n    \u003ctd\u003eLocal Modifications\u003c/td\u003e\n    \u003ctd\u003eSubstantial changes to make them compatible with NpmCommandLineRunner.\u003c/td\u003e\n  \u003c/tr\u003e\n\u003c/table\u003e\n","funding_links":[],"categories":["Java","JavaScript","javascript","Java (78)","VI. Program languages and applications that were written with Java","Compilers"],"sub_categories":["3. Javascript"],"project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fgoogle%2Fclosure-compiler","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fgoogle%2Fclosure-compiler","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fgoogle%2Fclosure-compiler/lists"}