ClosureJavascriptFramework
ClosureJavascriptFramework copied to clipboard
Sync debug and assert files should not always use the configured output wrapper.
When generating the typical asynchronously loading assert and debug code, the configured outputWrapper is ignored. When the synchronous files are created, they use the compiler and wrap the code in that wrapper. This is causing problems when wrapping the compiled code in an anonymous function, preventing the synchronous debug and assert libraries from working.
Add an option to the compiler plugin that requests the synchronous debug and assert output ignore any configured outputWrapper.