feat(@angular-devkit/build-angular): add webpack transformer to extract-i18n builder

[just-jeb]

The purpose of this PR is to add a Webpack configuration transformer in order to support i18n for custom webpack builds (3rd party builders).
More info here.

[julkue]

Related issue: #16679

[alan-agius4]

Can you please add Closes: #16679 as the commit footer and address the lint issue?

Thanks.

[just-jeb]

Done

[dgp1130]

Need to determine when the new i18n extraction method is coming up. Based on that timeline we can decided whether this PR should be done now or wait for the new infrastructure.

[julkue]

@dgp1130 What do you mean with that?

Need to determine when the new i18n extraction method is coming up

[dgp1130]

@julmot, there's some infrastructure work coming up changing the way our i18n pipeline works. I don't know much more than that at the moment, so we just need to figure out the expected timeline for that work to understand whether it makes sense to do this work now or wait to integrate it with the new infra.

I forget who told me they were looking into this. @clydin, who's the right person to talk to about the i18n pipeline?

[julkue]

Sorry to ping @clydin, but I'd very much appreciate any progress here since I can't use xi18n currently due to the need of my custom webpack config.

[julkue]

Is there anyone that could reply to @dgp1130's question?

[petebacondarwin]

The new infrastructure work mentioned is based on this PR: angular/angular#32912

I need to work on this in the next few weeks, then it can be integrated into the CLI.

[julkue]

@petebacondarwin Any news on this? Really need it.

[julkue]

Is there any chance we can merge this?

[clydin]

Superseded by #18613 and will be in 10.1.0.

[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.}