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
trying to use vue-i18n #216
Comments
@francoisp This happens because the version of the We'll change this version number to the Vue.js version we forked from, in the next release. Since the version was |
ok awesome! Where would I edit this to test locally? FWIW I've also come across vuex-i18n, that one works with vue-native-core (also it uses vuex for lazy loading), but the rest of my stuff uses nuxt-i18n and that leverages vue-i18n... I'd like to use the same format for i18n in native and web artifact... At first glance vuex-i18n looks leaner and more flexible, but nuxt-i18n nails it for SSR as well as apps. |
You could edit build.js in the vue-native-core node module. There should be
a line similar to
```
Vue.version = '0.1.4';
```
Line 3863 in the latest release.
We haven't tested the other libraries you mentioned yet, although they
should work fine if they are independent of browser APIs.
…On Fri, 18 Oct 2019, 22:04 Francois Payette, ***@***.***> wrote:
ok awesome! Where would I edit this to test locally?
FWIW I've also come across vuex-i18n, that one works with vue-native-core
(also it uses vuex for lazy loading), but the rest of my stuff uses
nuxt-i18n and that leverages vue-i18n... I'd like to use the same format
for i18n in native and web artifact... At first glance vuex-i18n looks
leaner and more flexible, but nuxt-i18n nails it for SSR as well as apps.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#216?email_source=notifications&email_token=AHLPOV7J7FLQNJ5RXGRN773QPHQRVA5CNFSM4JB7OVS2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEBVB6KI#issuecomment-543825705>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AHLPOV6KHD4VFLS2DZSCUBTQPHQRVANCNFSM4JB7OVSQ>
.
|
thanks for the quick answer! I tried updating the Vue.version in the build file, but now I get
vue-i18n seems a bit more integrated; I'm thinking I might just stick to translations in a json format instead of the fancy promise alternative that vue-i18n and nuxt-i18n offer; that way the same json files can be used for vuex-i18n... |
excuse me, could someone integrate i18n to an a vue-native project? thanks |
I am using i18n-js for my vue-native_expo project and it could work as expectation. You can try it |
Vue.prototype._i18n = i18n must be under the line App.mpType = 'app' App.mpType = 'app'
Vue.prototype._i18n = i18n |
@doubleh311 How to use i18n-js in Vue Native project I can't be able to use i18n.t('') |
Tried to use vue-i18n with vue-native-core, and when attempting use with
I get this warning: [vue-i18n] vue-i18n (undefined) need to use Vue 2.0 or later (Vue: 0.1.4). Then when using $t() I get this error: [Vue warn]: Property or method "$t" is not defined on the instance but referenced during render. Make sure to declare reactive data properties in the data option.
The text was updated successfully, but these errors were encountered: