Re: [FalconJX] Debugging minified code

2017-07-12 Thread Harbs
Yes. That works too: -js-compiler-option='--debug' -js-compiler-option='--formatting PRETTY_PRINT' Thanks. > On Jul 12, 2017, at 6:11 PM, Alex Harui wrote: > > In theory, you should have been able to use -js-compiler-option more than > once. > > -Alex > > On 7/12/17, 6:53 AM, "Harbs" wrote:

Re: [FalconJX] Debugging minified code

2017-07-12 Thread Alex Harui
In theory, you should have been able to use -js-compiler-option more than once. -Alex On 7/12/17, 6:53 AM, "Harbs" wrote: >Thanks. That does in fact work. > >Here’s what I used: >-js-compiler-option='--formatting PRETTY_PRINT --debug' > >Of course, I’m not sure how helpful this is because it lo

Re: [FalconJX] Debugging minified code

2017-07-12 Thread Harbs
Never mind. There was an error in my app that was preventing the minification and the step that renames things. It is renamed, but to legible names. This should prove very useful! :-) Interesting to note: Even after renaming and combining lots of lines (pretty printing is still VERY dense), my

Re: [FalconJX] Debugging minified code

2017-07-12 Thread Harbs
FYI, here’s a sample of what the code looks like with those options enabled.[1] Harbs [1]https://paste.apache.org/OM4H > On Jul 12, 2017, at 5:03 PM, Harbs wrote: > > Never mind. There was an error in my app that was preventing the minification > and the step th

Re: [FalconJX] Debugging minified code

2017-07-12 Thread Harbs
Thanks. That does in fact work. Here’s what I used: -js-compiler-option='--formatting PRETTY_PRINT --debug' Of course, I’m not sure how helpful this is because it looks like nothing has been renamed. Every bug I’ve encountered that was specific to minified code was due to renaming in some way…

Re: [FalconJX] Debugging minified code

2017-07-12 Thread Josh Tynjala
You should include the dashes, and you should surround everything in quotes. I think you put spaces between each option, but I've never used more than one. Here's a Closure option I've successfully used: -js-compiler-option="--compilation_level SIMPLE_OPTIMIZATIONS" - Josh On Tue, Jul 11, 2017

Re: [FalconJX] Debugging minified code

2017-07-12 Thread Harbs
Sometimes it’s not too hard to figure out what’s going on, but sometimes it’s a real pain. The situation where I had a comparison against a constant in a bindable class was a real doozy. It was in the middle of a lot of XML parsing and I originally thought there was a problem with the XML classe

Re: [FalconJX] Debugging minified code

2017-07-11 Thread Alex Harui
Try using -js-compiler-option. It should pass along the various options in the article to GCC. I haven't had to debug anything really big, but I often delete the source map, add line breaks to the area of code that is failing and step through it. Painful for sure, but often successful. HTH, -Al