Skip to content

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

Closed
zh99998 opened this issue Apr 7, 2017 · 6 comments
Closed

JIT I18n support #5869

zh99998 opened this issue Apr 7, 2017 · 6 comments

Comments

@zh99998
Copy link

zh99998 commented Apr 7, 2017

Bug Report or Feature Request (mark with an x)

- [ ] bug report -> please search issues before submitting
- [x] feature request

seems angular-cli now only support i18n with AOT build?
it's hard during development without JIT compiler..

@Angular2Guy
Copy link

Have look at issue #3540

@filipesilva
Copy link
Contributor

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

@mashbrno
Copy link

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!

@kwiesmueller
Copy link

I think I stumbled into this Problem.
So to clarify, the description shown in the docs using JIT won't work?

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?
So we would need JIT but "by accident" I now find this issue telling me, JIT is not supported?

@mashbrno
Copy link

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

@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 8, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants