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%7Cfa7b1b5a7b34438794aed2c178decee >1%7C0%7C0%7C636354107193335204&sdata=VYIC%2FYV7hx9DlzfD7II5mqvvmavD6Us1LZA >FkbQN%2BPs%3D&reserved=0>
