Optimizing initial load

[rsreimer]

Hi

I am in the process of migrating a large Ionic Angular project from Webpack Module Federation to Native Federation.

I am running into some issues due to implementation differences in the two federation solutions.
One issue is the number of requests in the initial load of Ionic when sharing it.

The @ionic/core package has a large amount of secondary entries, and most of them are loaded even in the simplest Ionic app, as demonstrated here:
https://github.com/rsreimer/ionic-native-federation
https://rsreimer-ionic-native-federation.netlify.app

The site sends ~190 requests just to load @ionic/core, which seems quite excessive.
With Webpack i have the option to bundle @ionic/core and all its secondary entries into a single js file, and therefore reduce it to a single request.

Does something similar exist for Native Federation or esbuild?

I have tried the build: 'package' and chunks: false sharing options, since the documentation seems to suggest it as a solution, but it does not bundle @ionic/core as one js file.
https://native-federation.com/docs/core/sharing.html

[mikkel-ol]

@Aukevanoost Do you have any inputs on this?

[Aukevanoost]

Hi, that is currently not a feature yet on native-federation. The main issue is that imports are not rewritten yet to support a monofile external.
I do think this is doable though, so feel free to create a feature request.

The nice thing about having so many files is that they can be downloaded in parallel. And that you only download the files that you actually need/import rather than waiting for 1 big JS file that contains everything. But I do agree that it might be nice to have the extra option.