JSlim is a JavaScript optimizer based on the Google Closure Compiler, but instead of optimizing your code it removes unused code. Some people call this type of application a tree shaker because it shakes unused code out of your tree.
Most websites use JavaScript libraries like JQuery or Prototype, but they don't use the whole library. JSlim builds you a new version of your favorite JavaScript library with only the code you're using.
JSlim is your favorite JavaScript library, only faster
This project builds with Gradle. Make sure to download 3.0.0 or later. Build the application by running gradle in the project root directory.
This project builds and runs on Windows, Mac, and Linux.
java JSlimRunner [options...] arguments...
--charset VAL : Input and output charset for all files
. By default, we accept UTF-8 as input
and output US_ASCII
--compilation_level [WHITESPACE_ONLY | : Specifies the compilation level to use
SIMPLE_OPTIMIZATIONS | ADVANCED_OPTIM : . Options: WHITESPACE_ONLY, SIMPLE_OPT
IZATIONS | NONE] : IMIZATIONS, ADVANCED_OPTIMIZATIONS
--externs VAL : The file containing javascript externs
. You may specify multiple
--flagfile VAL : A file containing additional command-l
ine options.
--formatting [PRETTY_PRINT | PRINT_INP : Specifies which formatting options, if
UT_DELIMITER] : any, should be applied to the output
JS. Options: PRETTY_PRINT, PRINT_INPUT
_DELIMITER
--help : Displays this message
--js VAL : The javascript filename. You may speci
fy multiple
--js_output_file VAL : Primary output filename. If not specif
ied, output is written to stdout
--lib_js VAL : The javascript library filename. You m
ay specify multiple
--logging_level [ALL | CONFIG | FINE | : The logging level (standard java.util.
FINER | FINEST | INFO | OFF | SEVERE : logging.Level values) for Compiler pro
| WARNING] : gress. Does not control errors or warn
ings for the JavaScript code under com
pilation
--no_validate : Pass this argument to skip the pre-par
se file validation step. This is fast
er, but won't provide good error messa
ges if the input files are invalid Jav
aScript.
--print_tree : Prints out the parse tree and exits
--separate_files : Pass this argument to separate library
files and the regular files into diff
erent output files. By default they a
re combined into a single file.
--skip_gzip : Skip GZIPing the results
This repository includes a number of sample application you can use to try JSlim with. The easiest place to start is with a simple JQuery/underscore.js. You can slim it like this:
gradle
build/install/jslim/bin/jslim --js_output_file out.js --js main.js --lib_js libs/jquery-1.7.2.js --lib_js libs/underscore.js
Once that command is done you can open the index.html file in your favorite browser and watch it run just the parts of JQuery and Underscore the page really needs. The page shows one of the basic underscore.js examples and looks like this:
2,4,6,8
Miaow my name is Charlie
Miaow my name is Fluffy
Miaow my name is Mouse
This process will remove 163 out of 410 named functions (39.7 percent) and reduce the total size of the library files by 28 percent.
JavaScript organizes blocks of code into functions. Some functions are named and stand alone like this:
function myFunction() {
alert('hey there');
}
Other functions are organized into JavaScript closures like this:
var myObj = {
myFunction: function() {
alert('hey there');
}
};
JavaScript libraries provide functions like that and you call them in your code. JSlim figures out which functions you're calling, and which ones they're calling, and removes the rest.
JSlim can track most function calls, but there are some where it can't follow what you're calling. The easiest way to break JSlim is using the eval function like this:
function myFunction() {
alert('hey there');
}
eval('myfunction();');
JSlim can't follow this function call to myFunction since it is part of an evaluated string. In this case you must reference myFunction as an external reference. Many JavaScript library do dynamic loading like this, especially for effects.
Let's say you write some JavaScript which looks like this:
o = {
f1: function() {
alert("I'm func 1");
},
f2: function() {
alert("I'm func 2");
}
};
o.f1();
JSlim looks at this code and determines that f1 is called, but f2 isn't. In this case it will remove f2 and make the code smaller and faster. If you start using f2 just run JSlim again and it will create a new library with it included.
JSlim works very differently depending on the library it's slimming down. The more a library uses named functions with simple dependencies and clean hierarchy the more we can slim it down.
JSlim doesn't work well with libraries using mostly anonymous functions and other constructs which are difficult to track down. JSlim is also strictly a static code analysis tool which means it doesn't run any JavaScript code.
For example, if your code looks like this:
function f(flag) {
if (flag === 1) {
alert($.now());
} else if (flag === 2) {
$.noop();
}
}
...JSlim will keep the now function and the noop function since it can't tell what the value of flag might be.
JSlim is best with a simple JQuery/underscore.js application where it reduces the total size of the libraries by 28% above using the Closure compiler and GZIPing. Most libraries are reduced by 10-20 percent, but the savings in total size is only part of the story.
Most JavaScript compressors make your code smaller by removing whitespace and comments and inlining functions. JSlim actually removes code which reduces computational complexity. The means your libraries aren't just smaller, but they actually run faster.
How is JSlim different from Closure [Advanced Optimizations] (https://developers.google.com/closure/compiler/docs/api-tutorial3)
The Google Closure Compiler supports an [ADVANCED_OPTIMIZATIONS] (https://developers.google.com/closure/compiler/docs/api-tutorial3) advanced compilation mode which handles dead code removal as well as other features.
JSlim focuses on removing dead code from third-party libraries which aren't compatible with ADVANCED_OPTIMIZATIONS. It also dependencies dynamically instead of requiring an externs file.
JSlim and ADVANCED_OPTIMIZATIONS work well together.
JSlim is at release 0.1. It's pretty stable, but hasn't had a large amount of testing yet. I've tested JSlim with the following libraries:
JSlim should work with any library. It can also work directly with your JavaScript. Write as many functions as you want and JSlim will prune out the unused ones so your code stays small and your site stays fast.
In the short term I'm focusing on improvements to the core compilation process. I want to improve the algorithm and remove more of the unused functions. This especially means focusing on anonymous functions.
I also want to write JSlim plugins for Apache Ant and Apache Maven. That way you can run JSlim as part of your build. I'm still working on it.
I'd also like to thank the Google Closure Compiler team for all of their help, support, encouragement, and excellent compiler. JSlim stands on the shoulders of the Closure Compiler.
JSlim could build with Ant or Maven, but I wanted a new project to try out Gradle. I stuck with Gradle because it's awesome. Check out my gradle.build file and see how easy it is to make a complex build in Gradle.
I'm happy for any feedback you have on this project. It is still in the early stages and I'm still working out the best heuristics. JavaScript is a very weakly typed language and optimizing it is tricky.
If you have time to try it out or any suggestions for how I can make JSlim better please send me an email.
This project is available under the Apache License, Version 2.0.