You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 1, 2020. It is now read-only.
I totally get that this cannot just be implemented in app-scripts as this has to follow after conscious decisions of the developer, but e.g. step 1 and 3 could (at least) partially be supported by app-scripts out of the box.
For PWAs this would make a real difference.
(Of course it would be a valid decision to say that this is out of scope and should be handled the way Julien did - manually)
The text was updated successfully, but these errors were encountered:
Hello @janpio , thanks for opening an issue with us. I agree that Julien's setup and his results are pretty awesome, but the cool thing is with some of the new stuff we have coming on the framework side of things, this issue is going to be solved without having to do any of the build magic that Julien was doing. In a future release of Ionic-Angular every component will lazy load only the css needed at that time. So if its on an Android device or on the web as a PWA it will only lazy-load the css needed for MD mode, and none of the other mode's css will get loaded. Also, as i said, its going to be lazy loaded per component, so you are only ever loading the css needed specifically for the components on that page. So, while this is a very cool setup, in the near future it will not be needed anymore.
Julien Renaux showed in his Optimized Ionic-Angular CSS Bundle for PWAs post how he removed 91% of the CSS for his app. He did this by:
mode
of the app to one platform and filter out all CSS for the left out platforms: https://julienrenaux.fr/2017/07/20/optimized-ionic-angular-css-bundle-for-pwas/#Build_for_one_platform_onlyI totally get that this cannot just be implemented in app-scripts as this has to follow after conscious decisions of the developer, but e.g. step 1 and 3 could (at least) partially be supported by app-scripts out of the box.
For PWAs this would make a real difference.
(Of course it would be a valid decision to say that this is out of scope and should be handled the way Julien did - manually)
The text was updated successfully, but these errors were encountered: