-
Notifications
You must be signed in to change notification settings - Fork 372
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Apply auto-recompile to all codeserver compilations #9437
Comments
I think we should aim at replacing c.g.g.dev.DevMode with a "devserver" (possibly baked into CodeServer, but not necessarily) similar to Webpack:
That way:
|
Proof-of-concept devserver at https://github.com/tbroyer/gwt-devserver |
Whoa, I like the sounds of it. |
By the way, there is another way around funky web app configurations. That's use the Compiler with incremental, to compile into the output directory with only one permutation for testing quickly. Then it doesn't matter if it's ssl, or has odd directory. The only issue here, is the web servlet container, or hosting container has to know about the new resources pushed into it, and refresh. |
Currently only the codeserver first compilation or the launcherDir output uses the LauncherDir.generateStubNocacheJs (i.e. the app.nocache.js that recompile on reload). Is this some kind of limitation? Is it possible to use the auto-recompile.nocache.js for all Recompilations?
This is specially useful to get rid of devmode. Currently if you have a client only or a CORS enabled app, and you put your index.html inside your app module public folder, you can use the codeserver to bootstrap your app. The unique actual disadvantage compared to devmode is that devmode uses the auto-recompile.nocache.js but codeserver doesn't.
The text was updated successfully, but these errors were encountered: