Timeline for Debugging Closure-compiler Compiled Javascript
Current License: CC BY-SA 3.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 12, 2013 at 13:14 | history | edited | Chad Killingsworth | CC BY-SA 3.0 |
Rewrote title to better reflect the actual question
|
| Jan 3, 2013 at 23:55 | vote | accept | Hamish | ||
| Jan 3, 2013 at 23:55 | answer | added | Hamish | timeline score: 1 | |
| Jan 3, 2013 at 22:00 | answer | added | case nelson | timeline score: 0 | |
| Jan 3, 2013 at 21:46 | history | edited | Chad Killingsworth |
Add dojo tag
|
|
| Jan 3, 2013 at 21:46 | answer | added | Chad Killingsworth | timeline score: 10 | |
| Jan 3, 2013 at 21:41 | comment | added | Hamish |
@Bart SIMPLE_OPTIMIZATIONS - there are no with statements in the code base, and a single eval that is trivial and definitely unrelated to the bug I'm seeing.
|
|
| Jan 3, 2013 at 21:30 | comment | added | Bart | What optimization level are you using? You can read about some limitations of the closure compiler here: developers.google.com/closure/compiler/docs/limitations | |
| Jan 3, 2013 at 21:28 | comment | added | Hamish | @AlexWayne Definitely want to keep Closure - the dojo build system works particularly well with it. | |
| Jan 3, 2013 at 21:26 | comment | added | Alex Wayne | No clue. But you may want to give UglifyJS a shot. I'm a big fan. | |
| Jan 3, 2013 at 21:22 | history | asked | Hamish | CC BY-SA 3.0 |