FYI, here’s a sample of what the code looks like with those options enabled.[1]

Harbs
[1]https://paste.apache.org/OM4H <https://paste.apache.org/OM4H>

> On Jul 12, 2017, at 5:03 PM, Harbs <harbs.li...@gmail.com> wrote:
> 
> 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 app is still over 62,000 lines. It’s pretty 
> impressive how well the compilers do with an app of this size. :-)
> 
> Harbs
> 
>> On Jul 12, 2017, at 4:53 PM, Harbs <harbs.li...@gmail.com> 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 looks like nothing 
>> has been renamed. Every bug I’ve encountered that was specific to minified 
>> code was due to renaming in some way…
>> 
>> Harbs
>> 
>>> On Jul 12, 2017, at 4:15 PM, Josh Tynjala <joshtynj...@gmail.com> wrote:
>>> 
>>> 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 at 11:35 PM, Harbs <harbs.li...@gmail.com> wrote:
>>> 
>>>> 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 classes
>>>> until a stepped through a lot of renamed functions that were very hard to
>>>> figure out what they did.
>>>> 
>>>> So what exactly would the compiler option look like?
>>>> 
>>>> I currently have something like this:
>>>> -remove-circulars -js-output-optimization=skipAsCoercions
>>>> -html-template=src/resources/mdl-js-index-template.html
>>>> -js-external-library-path+=typedefs -js-library-path+=lib
>>>> 
>>>> Do I include the dashes or not?
>>>> 
>>>> Is this correct?
>>>> -remove-circulars -js-output-optimization=skipAsCoercions
>>>> -html-template=src/resources/mdl-js-index-template.html
>>>> -js-external-library-path+=typedefs -js-library-path+=lib
>>>> -js-compiler-option=debug
>>>> 
>>>> How would I include multiple options there? Something like this does not
>>>> look right:
>>>> -js-compiler-option=debug,formatting=PRETTY_PRINT
>>>> 
>>>>> On Jul 12, 2017, at 8:33 AM, Alex Harui <aha...@adobe.com.INVALID>
>>>> wrote:
>>>>> 
>>>>> 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,
>>>>> -Alex
>>>>> 
>>>>> On 7/11/17, 3:42 PM, "Harbs" <harbs.li...@gmail.com> wrote:
>>>>> 
>>>>>> One of the difficult tasks is trying to figure out what’s going wrong in
>>>>>> minified code. I found an article on tips for that.[1] There are a few
>>>>>> Closure options to make the minified code more legible. Is there a way
>>>> to
>>>>>> have Falcon use those options when sending the code to Closure?
>>>>>> 
>>>>>> Thanks,
>>>>>> Harbs
>>>>>> 
>>>>>> [1]https://na01.safelinks.protection.outlook.com/?url=
>>>> https%3A%2F%2Fgithub
>>>>>> .com%2Fgoogle%2Fclosure-compiler%2Fwiki%2FDebugging-
>>>> Compiled-Code&data=02%
>>>>>> 7C01%7C%7Cbfca0e9dc888469da8e708d4c8b05d83%
>>>> 7Cfa7b1b5a7b34438794aed2c178dec
>>>>>> ee1%7C0%7C0%7C636354107193335204&sdata=VYIC%
>>>> 2FYV7hx9DlzfD7II5mqvvmavD6Us1L
>>>>>> ZAFkbQN%2BPs%3D&reserved=0
>>>>>> <https://na01.safelinks.protection.outlook.com/?url=
>>>> https%3A%2F%2Fgithub.c
>>>>>> om%2Fgoogle%2Fclosure-compiler%2Fwiki%2FDebugging-
>>>> Compiled-Code&data=02%7C
>>>>>> 01%7C%7Cbfca0e9dc888469da8e708d4c8b05d83%7Cfa7b1b5a7b34438794aed2c178de
>>>> cee
>>>>>> 1%7C0%7C0%7C636354107193335204&sdata=VYIC%
>>>> 2FYV7hx9DlzfD7II5mqvvmavD6Us1LZA
>>>>>> FkbQN%2BPs%3D&reserved=0>
>>>>> 
>>>> 
>>>> 
>> 
> 

Reply via email to