closure-compiler
closure-compiler copied to clipboard
google
A JavaScript checker and optimizer.
> // TODO(charleyroy): Add getTargetRanges() once a consensus has been made // regarding how to structure these values. See // https://github.com/w3c/input-events/issues/38. /** https://github.com/google/closure-compiler/blame/38f2f840f50c96a823babcc2540838faa733fbf0/externs/browser/w3c_event.js#L553-L556 In the mentioned TODO it mentions an...
This code: ```js class Super { /** * @nocollapse */ static method() { return 'foo'; } } class Sub extends Super {} console.log(Sub.method()); // should log 'foo' console.log(Sub.hasOwnProperty('method')); // should...
### There seems to be an issue with parsing composite character sequences. Composite character `İ` consist of the base character and combining character sequence (U+0049)(U+0307) Using this character causing the...
input code: ```ts function foo(arg) { switch(arg.type){ case 'foo': var _arg_foo; (_arg_foo = arg.foo) === null || _arg_foo === void 0 ? void 0 : _arg_foo.foo(); break; case 'bar': var...
I wonder if there is a reason why google closure-compiler can't convert the following snippet while Babel can do it. (Snippet available with the links below) Maybe somebody can help...
When debugging problems with unresolved import paths, it turned out that parsing import directives is triggered only when the directive actually starts the line: JsFileRegexParser:347 (in version 20220601) ``` if...
***Input*** ```ts function getFoo() { class Foo { } (() => { Foo.x = 1; })(); return Foo; } const Foo1 = getFoo(); class Bar { constructor(num) { this.num =...
`google/closure-compiler` intentionally [adds a line break](https://stackoverflow.com/questions/3018049/why-does-googles-closure-compiler-leave-a-few-unnecessary-spaces-or-line-breaks) after [every 500 characters](https://developers.google.com/closure/compiler/faq#:~:text=The%20Closure%20Compiler%20intentionally%20adds,effect%20on%20a%20script's%20semantics). Is there a way to prevent this behavior, and not add these line breaks, or could this be added as...
Compiler warnings like `WARNING - [JSC_UNREACHABLE_CODE] unreachable code` may often be suppressed by finding the corresponding diagnostic group and adding a `@suppress` tag, in this case `@suppress {uselessCode}`. We document...
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/#209
