Open petereijgermans11 opened 5 months ago
Hello @petereijgermans11 did you manage to migration from Webpack Module Federation to Native Module Federation?
I have not yet migrated to Native. I am also waiting for the mentioned fix in this issue.
Op wo 1 mei 2024 om 18:41 schreef ips219 @.***>
Hello @petereijgermans11 https://github.com/petereijgermans11 did you manage to migration from Webpack Module Federation to Native Module Federation?
— Reply to this email directly, view it on GitHub https://github.com/manfredsteyer/ngx-build-plus/issues/403#issuecomment-2088743823, or unsubscribe https://github.com/notifications/unsubscribe-auth/ABYF43ELBSG2F5SZ7NS5CQ3ZAELLXAVCNFSM6AAAAABBVJFUF2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBYG42DGOBSGM . You are receiving this because you were mentioned.Message ID: @.***>
Is it possible to implement the following feature in esbuild and in angular.json for 'Native Module Federation'? At this moment I use Angular 17 with 'Webpack Module Federation' and I want to step over to 'Native Module Federation'.
In Angular with 'Webpack Module Federation' you have the configuration option in angular.json to define an extraWebpackConfig. Esbuild does not support such a configuration option.
Why do I need this option? I want different configuration files for different tasks (e.g. build and serve, e2e).
It would be very useful for my installation for Native Module Federation in Angular 17 to have for example the configuration option: extraEsBuildConfig in angular.json