Any ideas on how to use Google Closure Compiler to combine multiple JavaScript files w/o any optimizations? Specifically, we want to use Closure to deploy two versions of our combined site JavaScript: release and debug. For release, we are using --compilation_level SIMPLE_OPTIMIZATIONS --manage_closure_dependencies which is working as intended. However, for debug, we would like our JavaScript to be combined intact/unmodified for easier debugging. It seems the minimum level of optimization is WHITESPACE_ONLY, any ideas would be appreciated.
views:
101answers:
2
A:
Two thoughts come to mind immediately. First - Why use closure compiler for that task, why not just something like cat jsfile1.js jsfile2.js > debug.js? Second - Closure Inspector will allow you to debug code compiled with Closure Compiler using FireBug.
To help you work with your transformed code, you can also install the Closure Inspector, a tool that makes it easy to use the Firebug JavaScript debugger with the Compiler's output.
gnarf
2010-07-07 21:25:37
We can't simply concatenate the JavaScript files in debug, because we still depend on closure to manage JavaScript dependencies. I will look into using Closure Inspector, the only challenge would be if we need to debug an issue in another browser.
HOCA
2010-07-07 21:31:58
A:
Turns out there's an option to format the processed JavaScript file using the --formatting PRETTY_PRINT. The option indents/formats (with whitespace) the output JavaScript file, such that the JavaScript is easily debuggable.
Wish the documentation is a little more detailed/complete :)
HOCA
2010-07-08 00:50:46