NO LONGER MAINTAINED
Laravel 5 package that allows you to share your Laravel localizations with your vue front-end, using vue-i18n or vuex-i18n.
Configuration paths have changed in Laravel 5.7, in order for this package to function properly you need to configure correct paths for jsPath and jsFile in your config\vue-i18n-generator.php
.
In your project:
composer require martinlindhe/laravel-vue-i18n-generator --dev
For older versions of the framework:
Register the service provider in config/app.php
MartinLindhe\VueInternationalizationGenerator\GeneratorProvider::class,
Next, publish the package default config:
php artisan vendor:publish --provider="MartinLindhe\VueInternationalizationGenerator\GeneratorProvider"
Next, you need to install one out of two supported VueJs i18n libraries. We support vue-i18n as default library. Beside that we also support vuex-i18n.
When you go with the default option, you only need to install the library through your favorite package manager.
npm i --save vue-i18n
yarn add vue-i18n
Then generate the include file with
php artisan vue-i18n:generate
Assuming you are using a recent version of vue-i18n (>=6.x), adjust your vue app with something like:
import Vue from 'vue';
import VueInternationalization from 'vue-i18n';
import Locale from './vue-i18n-locales.generated';
Vue.use(VueInternationalization);
const lang = document.documentElement.lang.substr(0, 2);
// or however you determine your current app locale
const i18n = new VueInternationalization({
locale: lang,
messages: Locale
});
const app = new Vue({
el: '#app',
i18n,
components: {
...
}
}
For older vue-i18n (5.x), the initialization looks something like:
import Vue from 'vue';
import VueInternationalization from 'vue-i18n';
import Locales from './vue-i18n-locales.generated.js';
Vue.use(VueInternationalization);
Vue.config.lang = 'en';
Object.keys(Locales).forEach(function (lang) {
Vue.locale(lang, Locales[lang])
});
...
npm i --save vuex-i18n
yarn add vuex-i18n vuex
Next, open config/vue-i18n-generator.php
and do the following changes:
- 'i18nLib' => 'vue-i18n',
+ 'i18nLib' => 'vuex-i18n',
Then generate the include file with
php artisan vue-i18n:generate
Assuming you are using a recent version of vuex-i18n, adjust your vue app with something like:
import Vuex from 'vuex';
import vuexI18n from 'vuex-i18n';
import Locales from './vue-i18n-locales.generated.js';
const store = new Vuex.Store();
Vue.use(vuexI18n.plugin, store);
Vue.i18n.add('en', Locales.en);
Vue.i18n.add('de', Locales.de);
// set the start locale to use
Vue.i18n.set(Spark.locale);
require('./components/bootstrap');
var app = new Vue({
store,
mixins: [require('spark')]
});
You can specify the output formats from es6
, umd
, or json
with the --format
option. (defaults to es6
)
php artisan vue-i18n:generate --format {es6,umd,json}
php artisan vue-i18n:generate --format umd
An UMD module can be imported into the browser, build system, node and etc.
Now you can include the generated script in the browser as a normal script and reference it with window.vuei18nLocales.
<script src="https://github.com/martinlindhe/laravel-vue-i18n-generator/raw/master/{{ asset('js/vue-i18n-locales.generated.js') }}"></script>
// in your js
Vue.use(VueI18n)
Vue.config.lang = Laravel.language
Object.keys(window.vuei18nLocales).forEach(function (lang) {
Vue.locale(lang, window.vuei18nLocales[lang])
})
You can still require/import it in your build system as stated above.
One advantage of doing things like this is you are not obligated to do a build of your javascript each time a the translation files get changed/saved. A good example is if you have a backend that can read and write to your translation files (like Backpack). You can listen to a save event there and call vue-i18n-generator.
Sometimes you may want to generate multiple files as you want to make use of lazy loading. As such, you can specify that the generator produces multiple files within the destination directory.
There are two options:
--multi
--multi-locales
php artisan vue-i18n:generate --multi{-locales}
The generator adjusts the strings in order to work with vue-i18n's named formatting, so you can reuse your Laravel translations with parameters.
resource/lang/message.php:
return [
'hello' => 'Hello :name',
];
in vue-i18n-locales.generated.js:
...
"hello": "Hello {name}",
...
Blade template:
<div class="message">
<p>{{ trans('message.hello', ['name' => 'visitor']) }}</p>
</div>
Vue template:
<div class="message">
<p>{{ $t('message.hello', {name: 'visitor'}) }}</p>
</div>
The more sophisticated pluralization localization as described here is not supported since neither vue-i18n or vuex-i18n support this.
Under MIT