Microfrontend support

[felipeplets]

🚀 Feature request

Webpack 5 Module Federation API will be a game changer to the web.
So bringing support to Angular CLI once Webpack 5 is released and supported will also be a game changer to Angular projects using the CLI.

Command (mark with an x)

• new
• build
• serve
• test
• e2e
• generate
• add
• update
• lint
• xi18n
• run
• config
• help
• version
• doc

Description

Once Angular CLI support Webpack 5 #17555 it is important to also support its new API called Module Federation that allow sharing modules in runtime among applications.

Describe the solution you'd like

Support Webpack 5 Module Federation.

Describe alternatives you've considered

No alternative considered.

[ScriptedAlchemy]

Let me know if there is any assistance needed on Module Federation

[jpchavat]

Any news about Webpack 5 in the CLI?

[felipeplets]

@jpchavat #17555 tracks specifically the support to WebPack 5, this issue is only related to Module Federation.

But I don't believe we will see support to WebPack 5 in Angular CLI before it is released. https://github.com/webpack/webpack/releases

[ScriptedAlchemy]

Should we make progress towards it, perhaps on a pre-release branch. While maybe not a stable release to the public, I’ve been working with other large projects who are working on the upgrade paths and if any issues are uncovered, we are able to address them at webpack ahead of the full release. Feedback from large projects is very valuable - W5 has been very stable.

[naveedahmed1]

Can anyone please share what specific impact and improvements it can bring in case of Angular applications?

[BenRacicot]

I can weigh in here after being part of a POC for an Angular upgrade on a massive group of applications (which most of us probably use regularly).

Regarding module sharing, several contacts have confirmed that they are lazy-loading their feature modules by referencing their import statements. A huge list of them... (import mapping)

Here is a stackblitz example

When it comes to architecting shared modules federation is not trivial, it is the correct tool for the job. Now when you extend this architectural need to sharing ACROSS applications we require specific tooling for this, not just a "bag of tricks".

Additionally, the way WP5 "shares" packages across these modules is super pro.

For large-enormous projects WP5 is not a nice-to-have, it will be a difference-maker. I implore the Angular team to make this happen ASAP even asking the community for help if needed.

[ScriptedAlchemy]

It stretches beyond angular apps to the JS ecosystem.

Attempts to split up applications but still share resources has always been cumbersome and clunky.

Angular apps would be able to scale beyond organization and deploy limitations. Since Angular is a framework, you're well positioned to leverage the new architecture for the best benefit of users.

Many large companies are crippled by scale issues and the overhead of trying to manually manage some form of organizational scalability around their codebases.

The capabilities that module federation brings to the table are an absolute must for any organization with a lot of code that wants to reduce management complexity and improve user experience while maintaining team autonomy.

I too am willing to help with the integration. It opens doors to build much bigger apps and the sharing mechanics is top tier.

The scale I typically with within is dozens to hundreds of teams or apps that all need to share or work together. Some of my largest systems I designed module Federation to cater towards have a header bar that consists of 15 separate teams with about 20 devs per team.

At any given point I can have 5-30 micro-frontends powering a given view.

The key point here is that module federation enables us to require code from independently deployed apps at runtime. And it's something we need

[BenRacicot]

Zack, I'm glad we are having the same experience(s) architecting modules/components across apps @ScriptedAlchemy.

I hope this is not a debate but rather community interest in how engineers will utilize WP5's federation tools. That being said I must insist that small projects who setup for lazy-loading (without the router) are being forced to use import mapping, that is listing the paths and import statements for each module the app may lazy-load.

import mapping our modules is painfully antiquated and as Zack Jackson brought out it needs to be remedied for all JS usage. But here we bring our experience to the Angular community/team.

[ydmitry]

Any news on branch or official fork with webpack 5 ?

[alan-agius4]

@clydin has been working on adding initial support for Webpack 5.

Unfortunately, supporting Webpack 5 is not a trivial feat as there are a lot of breaking changes that we need to address while still maintain comparability with Webpack 4.

[ScriptedAlchemy]

Soon as a branch is up. Even broken, I can provide some guidance. I've upgraded several community projects to webpack 5 and have rewritten many plugins over the past several months.

Upgrading is complex. But we were able to do so with next js, through a lot of updating. Next still remains WP4 and WP5 compatible.

[AbdoDabbas]

Hi, thanks a lot for your work, I would like to ask if there's any news about the module federation support or if there's any workaround to work with WP4?

[ydmitry]

@AbdoDabbas workaround is to use this fork https://github.com/clydin/angular-cli , build it and use built version as a dependency
You may need to do the same with https://github.com/just-jeb/angular-builders/tree/master/packages/custom-webpack , there need few fixes
Then add ModuleFederation in extra webpack config

[tatsujb]

@clydin has been working on adding initial support for Webpack 5.

Unfortunately, supporting Webpack 5 is not a trivial feat as there are a lot of breaking changes that we need to address while still maintain comparability with Webpack 4.

I'm too noob to understand. why would the new version of angular / angular ClI need to be retro-compatible with Webpack 4?

I understand that that's a nice to have but isn't the implication with a user upgrading to the new angularCLI that he's not personally depending something that depends Webpack 4 and if he is it's up to him to fix that and until then stick with the old version of Angular CLI ?

The reverse problem arises from holding back an angular-cli release because it breaks retro-compatibility with an external dependency (that, I'm pretty sure no typical use-case dev will directly depend in their package.json)

Again I'm fine with if we do support retro compatibility. If it holds Angular-CLI back for months on end, though then I find that motive unjustifiable.

[ScriptedAlchemy]

Dual support isn't really hard to provide. It's more the work to update loaders. Then parse current installed version of webpack. If it's v5, have conditional require statements that either import the v4 loader or the v5 update.

Next runs like this, almost every loader or plugin I've upgraded has v4 support. Only real work is updating internal code to support the v5 hook api.

[alan-agius4]

Experimental opt-in support for Webpack version 5 have been added since v11.0.0-next.3.

See #18820 for more information.

At the moment this is still opt-in and shouldn’t be used for production builds, as certain Webpack plugins and loaders don’t yet work properly with Webpack 5.

That said, this issue is not about Webpack 5, but rather provide module federation support which does require Webpack 5 but is a different topic, so let’s please keep the discussion in this thread on module federation.

[ScriptedAlchemy]

Got it will do!

[ScriptedAlchemy]

I'm also working on a update to the webpack runtime. Which changes how apps start up. This would remove the async broundary required by mobile federation. And move it into the startup module direct in webpack

[ydmitry]

For anybody who are interested, created an example of Angular 11, Webpack 5 Module Federation and @angular-builders/custom-webpack (to opt-in with this one - need more resolutions):
https://github.com/ydmitry/angular11-webpack-module-federation-custom-webpack-builder

[ScriptedAlchemy]

We also have one under module federation examples. Consider PRing yours into it as well. We do need more non react examples for users

[ydmitry]

@ScriptedAlchemy didn't see it before, it's a new one, thanks! https://github.com/module-federation/module-federation-examples/tree/master/angular11-microfrontends

[Niaro]

@ScriptedAlchemy Hi! May I ask, did u experience serious performance degradation on serve after switching to W5?
My app takes 20-30 sec in hmr mode on any change to rebuild and serve using webpack 5... Remove it from the resolutions and its back to 2-3s...
Thanks in advance!

[ronnyek]

I could see lots of potential problems coming out of attempting to support this on the angular side.... (I'm by no means an expert on its inner workings), but I think if angular supported module federation, that could potentially revolutionize building and sharing components, and would definitely breathe new life into a code base.

[ashimjk]

any update on this?

[glebmachine]

Here is a few bugs, that will enable module federation:
#20428 (v12.0.0+)
#20429 (v11.0.3)

[hardikpatel043]

Any update? Can we please have ETA for this ?

[dgp1130]

We're starting some higher-level discussion to find the priority for this and what the right solution to this problem will look like. With Webpack 5 support in the CLI and the number of microfrontend talks at ng-conf this year, we understand there is a lot of desire for an official Angular solution here.

I would like to restructure the topic here to not be specific to Webpack 5 module federation, but rather about microfrontends as a use case. From our understanding, the desire here is to be able to deploy different parts of a single Angular application independently from one another and have them work together at runtime. Module federation is one possible way to solve that particular problem, but it could also be done other ways, and we don't want to rule them out. If you have other use cases beyond that, I recommend filing a separate issue so we can evaluate that use case more holistically.

[RoopanV]

Hi,
Do we have any update for Microfrontend support in Angular 15 or 16?

[martinmcwhorter]

Prior Art: Manfred Steyer has created Native Federation, a builder/bundler agnostic implementation of Module Federation.

This implementation has NO dependency on Webpack.

https://www.angulararchitects.io/aktuelles/announcing-native-federation-1-0/

[petereijgermans11]

Please take a look at this issue:
I have an issue for Extra configuration possibilities for Native Module Federation with Angular.

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