closure-compiler
closure-compiler copied to clipboard
google
A JavaScript checker and optimizer.
This was initially posted [to mailing list](https://groups.google.com/forum/#!topic/closure-compiler-discuss/NAJEIwckYeE), but no one replied, so here is the feature request. I have AMD module with following line: ```javascript define(['@detox/crypto', '@detox/dht', '@detox/utils', 'ronion', 'fixed-size-multiplexer',...
Closure compiler v20200614 in.js: ```js { function foo(p) { self["external1"](p) } console.log(foo()); console.log(foo()); } ``` Command: `java -jar ./closure-compiler.jar --js in.js --js_output_file out.js --compilation_level WHITESPACE_ONLY --formatting PRETTY_PRINT` out.js: ```js {...
```js /** @type {string[]} */ // ^ // JSC_TYPE_PARSE_ERROR: Bad type annotation. expected closing } const x = ["hi"]; ``` This is supported in both TypeScript and JSDoc. It would...
- The official doc on compilation levels doesn't explain that most checks get enabled in the ADVANCED compilation mode only: https://developers.google.com/closure/compiler/docs/compilation_levels - The Wiki page on compiler warnings misguides that...
It's quite common in the Node.js world to write Typedef with JSDoc without creating any variables, e.g., ```js /** * Parse the config and extract arguments from the `process.argv` array....
The syntax to import JSON modules uses [module import assertions](https://tc39.es/proposal-import-assertions/#intro), recently added to JS and HTML specs, and supported by Chrome (ref: [tc39/proposal-json-modules](https://github.com/tc39/proposal-json-modules), [crbug.com/1132413](http://crbug.com/1132413), [crbug.com/v8/10958](http://crbug.com/v8/10958)) ```javascript import json_object_name from './some_file.json'...
The following JavaScript program is silly but valid: ```javascript label: break label ``` If run, the `break` should jump to the code immediately after the `label:`, so effectively `label: break...
depending on the order of externs passed to closure-compiler, type definitions might be silently lost! while i wouldn't disagree that i should be taking better care with externs, it seems...
Netbeans gets confused trying to open this project because there are two pom files. Replacing `pom.xml` with `pom-main.xml` seems to fix this. Is there a reason that it is structured...
This issue was imported from Closure Compiler's previous home at http://closure-compiler.googlecode.com The original discussion is archived at: http://blickly.github.io/closure-compiler-issues/#986
