Status for Ionic Standalone Bundle Size RFC? about ionic-framework

[sean-perkins]

@cwoebker thanks for opening this issue. At this time I would encourage you to open a feature request or update this ticket to a feature request around the desired outcomes you are wanting from Ionic Framework.

We can then label the feature request to get feedback on the community's interest around these changes and we can use that to signal internally for prioritization.

--

My only initial concern with the recommendation in the linked thread is supporting both import patterns makes it extremely easy for a developer to import the "wrong" component that will be bundled in the main chunk. It offers a migration path, but we should work to remove this usage entirely if the limitation around bundlers cannot be resolved outside of separate entry points. I would recommend we deprecate the existing standalone component classes with any new entry points, to help guide developers before the next major release.

Personally I would love to get to:

import { IonButton } from '@ionic/angular/button';

but this requires either removing the IonicModule usage or migrating IonicModule to use the custom elements output instead of the lazy loaded components. This would be a net-neutral result on bundling, but could have runtime performance impacts for applications using only a small subset of Ionic components in their applications with IonicModule.

[thetaPC]

I wanted to touch base regarding this issue. As mentioned, this is better suited as a feature request rather than an ongoing issue. Since it hasn't been converted into a feature request yet, I'll be closing it for now. You're welcome to open a feature request whenever you're ready.