Support for custom webpack configurations

[DavidGoethCplace]

Command

I don't know which commands are affected

Description

My company uses webpack module federation (by WebpackModuleFederation plugin) for a step-by-step migration from angular-js to latest angular version.
The problem we face is that a development build is not working due to the 'ngDevMode is not defined' problem as it is already reported here: #25830

We can workaround this by defining the ngDevMode manually:

config.plugins.push(
new webpack.DefinePlugin({
      ngDevMode: config.mode === 'development'
}));

But that is an angular internal.
I would appreciate it if the AngularWebpackPlugin would handle that directly.

Describe the solution you'd like

A rudimentary custom webpack configuration support. So that at least simple custom webpack configurations are supported.

Describe alternatives you've considered

No response

[alan-agius4]

By design, custom webpack configurations are not supported. Employing such custom configurations directs you towards an undesirable path.

[DavidGoethCplace]

@alan-agius4 : If it is done by design what would be your suggestion? How would you solve the initial problem of module federation? As far as I know this is not possible without a custom webpack configuration.

You say my path is undesirable. What would be an alternative (desirable) path?

[alan-agius4]

The tracking of official microfrontend support can be found at #17556. However, it is important to note that there is currently no official support available.

Additionally, it's worth acknowledging that module federation is tied to the older build system utilizing Webpack, and it is not compatible with the new Esbuild pipeline, even with the use of custom plugins.

Nevertheless, there is an ongoing implementation by the community utilizing native import maps, which can be explored at https://www.npmjs.com/package/@angular-architects/native-federation.

[DavidGoethCplace]

ok, thank you

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}