Well, after patching CompilerOptionsImpl in gwt-codeserver.jar to return
true in isRunAsyncEnabled(), the code server started splitting the code,
but source maps were only generated for the initial fragment.
I don't know the internals, but shouldn't be terribly hard to have the
source maps for each split point, right? Or isn't it at all supported by
the compiler?
Compiling using "-saveSource -saveSourceOutput <dir>" together with
<set-property name="compiler.useSourceMaps" value="true" /> and
<set-configuration-property name="includeSourceMapUrl" value="true" />
correctly saves all sources in the output dir and sets the source map
comments on each script...
Also, the CompilerOptionsImpl has this:
@Override
public boolean shouldSaveSource() {
return false; // handling this a different way
}
This "different way" is explicitly not handling the runAsync case.
Is there a strong reason for this?
Thanks in advance.
Em sexta-feira, 14 de fevereiro de 2014 15h55min02s UTC-2, Luis Fernando
Planella Gonzalez escreveu:
>
> Hi.
> I'm recently attempting to use SuperDevMode, but our project is quite
> large, and the generated compiled .js has ~12MB.
> Chrome struggles (and hangs) when attempting to download source maps,
> making the whole debugging unpractical.
> Without SuperDevMode, we use code splitting, and the fragments are much
> more manageable.
> But SuperDevMode always compiles the application to a single .js file.
> Is it possible to use code splitting with SuperDevMode?
>
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to google-web-toolkit+unsubscr...@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/groups/opt_out.
