-
Notifications
You must be signed in to change notification settings - Fork 12k
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
Cannot extract i18n from library since angular 18 #29120
Comments
I18n extraction from multiple projects at once, and from libraries were never supported. I am not entirely sure how this worked in your case, but maybe you were using a non official builder or TypeScript path mappings? See: #17140 |
Yes, i use a path mapping
But no I follow the tip in #17140 and added "extract-i18n" in the architects section of my lib. But I get the following message by now:
So translating libraries isn't supported at all, although it is allegedly supported? https://v18.angular.dev/cli/extract-i18n |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Command
extract-i18n
Is this a regression?
The previous version in which this bug was not present was
17
Description
I have a multi-project workspace with 2 applications and 1 library, which uses all i18n. In angular 17 I could simply execute
ng extract-i18n
and all translations from all applications and the library were extracted in one single file.After updating to version 18 and executing
ng extract-i18n
the following message appears:So I have to extract the translations from each single application and the library isn't supported anymore?
Minimal Reproduction
ng extract-i18n
Exception or Error
Your Environment
Anything else relevant?
No response
The text was updated successfully, but these errors were encountered: