You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which @angular/* package(s) are the source of the bug?
localize, Don't known / other
Is this a regression?
Yes
Description
When a component using i18n and a directive with inputs with custom service for translation/localization purposes is packed as a library and installed in an Angular 17 project, translations no longer work (only default English values are populated).
Same code works in components that are defined in the application (not installed as a separate library/package), and the translations also work with "browser" build (with some additional configurations):
Everything also works as expected when updating Angular 16 application to 17, but not when installing the packages in a newly created Angular 17 application, so it seems the issue is caused by the new default build system - https://angular.io/guide/esbuild.
Which @angular/* package(s) are the source of the bug?
localize, Don't known / other
Is this a regression?
Yes
Description
When a component using i18n and a directive with inputs with custom service for translation/localization purposes is packed as a library and installed in an Angular 17 project, translations no longer work (only default English values are populated).
Same code works in components that are defined in the application (not installed as a separate library/package), and the translations also work with "browser" build (with some additional configurations):
Everything also works as expected when updating Angular 16 application to 17, but not when installing the packages in a newly created Angular 17 application, so it seems the issue is caused by the new default build system - https://angular.io/guide/esbuild.
Reproduction:
Archive.zip
Please provide a link to a minimal reproduction of the bug
No response
Please provide the exception or error you saw
No response
Please provide the environment you discovered this bug in (run
ng version
)Anything else?
Related issue:
telerik/kendo-angular#4195
The text was updated successfully, but these errors were encountered: