-
-
Notifications
You must be signed in to change notification settings - Fork 419
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
Add Support for Static Catalog #432
Conversation
I could successfully webpack i18n:
|
This looks promising - if only I had seen that at start of weekend. Will quickly review and merge next week... |
I'm quite happy with the solution and it seems to work as intended. However, I noticed some strange behaviour during testing. If you replace |
yap - main problem is that i18n currently still is tested as singleton. So tests with different settings may (...will) introduce side effects. One option to come around that singleton is to clear require cache. But there is another PR open for support of real instances. Plus I am planing a rewrite for 1.x branch. So for now I want to stick to existing tests as a POC for integration until code refactor is finished. And after that tests will get a refactor to get isolated with instances. Well, that's the plan... Meanwhile I do carefully reviews even if tests pass... :) |
@mashpie Any update on this? |
honestly... just entered gihub url in chrome a second ago too merge (I saw you comment appearing on second screen while checking commits) |
and released to npm as 0.10.0 |
In order to webpack i18n I want to statically set the catalog. This fixes #262.