Is it possible to build a production release without using AOT (templates will be JIT compiled by the client as it was with Angular1)?
If yes, will it still be possible using ionic-angular 4, or will AOT be made mandatory for production builds?
AOT isnāt just one thing. You might want to check about the angular compiler flags available for tsconfig.json. There are a lot of them, and I donāt understand them well. But sure, you can turn a lot of things off.
I need mobile Apps to get HTML templates from server, so that I can modify them, without resubmitting to App stores, like I always did with Angular 1.
I tried simply using a remote (HTTP) URL for a Component ātemplateUrlā and it works with a dev build, but I imagine it will not, if AOT is used, will it?
Since --prod implies --aot I wonder if is it possible to configure a build with --prod but not --aot.
Also I think I read somewhere (couldnāt find it again) that with Ionic 4 AOT will be mandatory, but Iām not sure about that.
// If context is prod then the following flags must be set to true
context.runAot = [
context.runAot,
context.isProd || hasArg(āāaotā),
].find(val => typeof val === ābooleanā);
So, if I want to try disabling AOT for --prod, I have to use a modified version of ionic-app-scriptsā¦
ā¦donāt knowā¦ it may be a little too much, Iāll have to think about itā¦
I would use that too. My app creates documents based on html and custom commands from server side and I canāt do that with AOT. Instead I use a build --release command (I have no idea if that is a think even), but my package is not well optimized.