Reputation: 1083
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.
Upvotes: 6
Views: 5135
Reputation:
Concatenation works like you'd expect it:
java -jar compiler.jar --js 1.js --js 2.js --js_output_file out.js
Upvotes: 4
Reputation: 14605
--formatting PRETTY_PRINT for beautifying
--debug true for meaningful names (after Advanced compilation)
Upvotes: 4
Reputation: 1083
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 :)
Upvotes: 2
Reputation: 106322
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.
Upvotes: 2