closure-compiler
closure-compiler copied to clipboard
google
A JavaScript checker and optimizer.
fixes #3840 - allow user to pass any path separator as --chunk_output_path_prefix as a user, you might want to use unix-style path separators always, since they're also compatible with windows....
This should resolve https://github.com/google/closure-compiler/issues/3957, which I believe was closed prematurely without a fix. This is needed because the closure-compiler jar is being flagged with CVE-2022-25647 as a result of the...
The contents of `test.js`: ```js let a = null; function b() { if(a != null) { console.log("not null"); } a = 0; } b(); document.getElementById("id").onclick = b; ``` Compiled with...
The `AsyncIterator#return` method should be called by closure-compiler's async iteration polyfills, but doesn't seem to be (compiling with advanced opts): ```shell $ node test.js > next: 0 > next: 1...
Closure throws an exception when I try to build source maps for chunks: java.io.FileNotFoundException: .\dist\closure\common.js.map (The system cannot find the path specified) It seems like there's a race condition issue...
The following used to be compiled away (in `v20210601`, even without the type annotations and the typeof): ```js // ==ClosureCompiler== // @compilation_level ADVANCED_OPTIMIZATIONS // @output_file_name default.js // ==/ClosureCompiler== /** *...
Example for https://closure-compiler.appspot.com: ```js // ==ClosureCompiler== // @compilation_level SIMPLE_OPTIMIZATIONS // @language_in ECMASCRIPT6 // @language_out ECMASCRIPT6 // @output_file_name default.js // @formatting pretty_print // ==/ClosureCompiler== this['stringview_iter'] = { 'pop'() { return Module['_BinaryenPop'](module,...
- Most methods in `Atomics` work only with unclamped integer-based TypedArrays. In the specs, it's either directly checked by [ValidateIntegerTypedArray](https://tc39.es/ecma262/multipage/structured-data.html#sec-validateintegertypedarray), or via [AtomicReadModifyWrite](https://tc39.es/ecma262/multipage/structured-data.html#sec-atomicreadmodifywrite). - `Atomics.notify` and `Atomics.wait` require waitable TypedArray...
Compilation level `BUNDLE` appears to include a lot of polyfill code, even for things supported by the language setting. The real problem though is this code relies on top-level `this`...
Peephole passes and others should not traverse into functions annotated with 'use asm'. The 'use asm' string needs to be retained.
