google-closure-compiler

Introduction I use Google Closure Compiler frequently for compressing my JavaScript files. Now, it seems to compress my code fairly well. Now, I try to make a habit of storing the this object in a local variable, because this cannot be obfuscated, but a local variable certainly can be obfuscated. However, Google Closure Compiler does not recognize this, and instead removes all instances of the local variable, replacing it with this . Regarding optimization... I am well aware that one should avoid pre-optimization when writing code. However, I feel that caching this is acceptable because doing

Please note: this question relates to the use of Google's Closure Compiler. It's not directly about ES6, since that part is working. I've written a class in ES6 which extends the native Date object. It's a large class, but this is a simplified version: class Dative extends Date { constructor (dateData) { super(); super.setTime(Date.parse(dateData)); } addMilliseconds (ms) { super.setTime(super.getTime() + ms); } } The code above works fine in Chrome and Firefox. However, when I pass it through Closure Compiler, it throws errors: Uncaught TypeError: Method Date.prototype.setTime called on

I am trying to automate a particular module in our JS library and am stuck at a point where I want to define a set of properties (lets say an object that goes as construction parameter of a class). /** * This function initiates world peace! * @constructor * @param {object} defaults - The options to initiate peace. * @param {number} defaults.issues - The number of issues being taken up. * @param {string} defaults.source - The name of the location where process starts. */ var WorldPeace = function (defaults) { // code here }; It is well and good had all properties of the construction was defined

I have a long script nicely wrapped into a (function() {/.../})() to avoid all kind of name pollution. It is 100% typed with zero warning. I found out that Google Closure compiler starts by redefining i and j in the global namespace which feels both unnecessary and dangerous, especially since I am compiling a script that has zero interference with the namespace. (the compiled script starts with var i=null,j=!1; , for compactness reasons I believe). I can think of a work around which is to wrap it using the --output_wrapper but I can't think of a reason why Google would pollute the namespace

I use Typescript command (tsc) to create a single Javascript file containing all plateform classes. tsc "./Main.ts" -out "./script/myProject_debug.js" --declarations Then, I want to obfuscate this file with Google Closure (compiler.jar) like this : java -jar ./compiler/compiler.jar --compilation_level ADVANCED_OPTIMIZATIONS --js "./script/myProject_debug.js" > "./script/myProject.js". But when I execute the resulting obfuscated/optimized code, I got this following error : Uncaught TypeError: Cannot read property 'prototype' of undefined Which matches the following non-obfuscated JS code

I'm trying to compile one of my HTML5 project using Google Closure. I'm recieving several errors that I don't know how to solve. In fact, it's the same error but for different variables. Here the errors messages: variable window is undeclared variable event is undeclared variable console is undeclared variable Audio is undeclared These variables are Javascript built-in variables. If I compile this same project directly in command-line, it works. But, in my case, I need to compile this project using an ant file (build process). My ant build script is using the same jar file that I use in