-
-
Notifications
You must be signed in to change notification settings - Fork 203
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Custom webpack @ extract-i18n | Angular 10.1 #659
Comments
Hi @julmot, thanks for bringing it up. As for now the
The required change is really small (like 3 lines of code), similarly to I totally agree it should be supported, however I'm not sure when I'll be able to take it. So if you want to speed things up I'd suggest you to create a PR to Angular CLI repo. As I mentioned the required change is really small. Whether you take it or not this feature request will be blocked until the transformer is supported in Angular. |
FYI, it's in progress: angular/angular-cli#16759. |
Great! Related issue: angular/angular-cli#16679 |
Another update (from Angular team):
So you can expect it soon after 9.1.0-beta is out. |
@just-jeb Any update on this? Angular 10.1.0 is already out and the webpackTransformer is included. |
Can't commit on a specific date but it's one of the top priorities now. As always, PRs are welcome. |
Unfortunately I can't anymore. After this has been idle from the ng team for so long, I've refactored my build process to avoid custom webpack configurations. |
Is your feature request related to a problem? Please describe.
I know that there has already been a discussion on this topic here and it has been implemented in Angular 7 by @patnolanireland, but it's still missing in Angular 8.
I need to build my application with a custom webpack config to configure webpack alias (namespaces). Currently I can't use the Angular extract i18n process because I can't tell it to use my custom webpack config. Therefore, it'll fail.
This was already officially supported in Angular 7, according to the docs.
Describe the solution you'd like
Implement the possibility to specify a custom webpack config for extract-i18n.
The text was updated successfully, but these errors were encountered: