-
Notifications
You must be signed in to change notification settings - Fork 12k
JIT I18n support #5869
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
Comments
Have look at issue #3540 |
This is the only supported approach in the CLI, yes. We don't have plans to support it in JIT since ng-i18n needs AOT compilation. You can submit a feature request in https://github.com/angular/angular |
If so, can you please update the official documentation? It refers to Angular CLI on top and describes JIT version below. At least put a big warning there! |
I think I stumbled into this Problem. When running ng i18n I am getting weird templating errors I don't get when building the app. But the docs tell me no other way to extract the messages. Maybe I did not understand AOT vs. JIT correctly, but building the app in different languages makes no sense to me, as it would require different deployments then, right? |
Yes, AFAIK JIT is not supported. Most of the users stick to a single language and the overhead of downloading, parsing and processing resource files on the client was simply too high. You can always deploy the application into subdirectories, eg. /en, /de, /jp |
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. |
Bug Report or Feature Request (mark with an
x
)seems angular-cli now only support i18n with AOT build?
it's hard during development without JIT compiler..
The text was updated successfully, but these errors were encountered: