Question

I found that some options in CompilerOption are not exported to the command line.

For example, alias all strings is available in the Closure Compiler’s Java API CompilerOption but I have no idea how set this in the command line.

I know I can create a new java class, like:

Compiler c = new Compiler();
ComppilerOptions opt = new ComppilerOptions();
opt.setAliasAllString(true);

c.compile(.....);

However I have to handle the command line args myself.

Any simple idea?

============================

In order to try the alias all string option, I write a simple command line application based on compiler.jar.

However I found that, the result I got when open the alias all string is not what I expected.

For example:

a["prototype"]["say"]=function(){
  var a="something string";
}

Given the above code, the something string will be replaced by a variable like this:

var xx="something string";

....
var a=xx;
....

This is fine, but how about the string “say”? How does the closure compiler know this should be aliased(replace it use variable) or exported(export this method)?

This is the compiled code now:

a.prototype.say=function(){....}

It seems that it export it.

While I want this:

var a="prototype",b="say",c="something string";

xx[a][b]=function(){.....}

In fact, this is the google_map-like compilation.

Is this possible?

Answer 1

Not all options are available from the command line – this includes aliasAllStrings. For some of them you have the following options:

1. Build a custom version of the compiler
2. Use the Java API (see example).
3. Use plovr

Getting the same level of compression and obfuscation as the Maps API requires code written specifically for the compiler. When properly written, you’ll see property and namespace collapsing, prototype aliasing and a whole host of others. For an example of the style of code that will optimize that way, take a look at the Closure Library.