Closed tomocrafter closed 3 years ago
Thank you for your reporting! Unfortunately, I could not reproduce this issue.
I hope you would like to run the vue inspect
in your project.
Then you will get the information in the webpack config:
...
...
/* config.plugin('vue-i18n-feature-flags') */
new DefinePlugin(
{
__VUE_I18N_LEGACY_API__: 'true',
__VUE_I18N_FULL_INSTALL__: 'true',
__VUE_I18N_PROD_DEVTOOLS__: 'false'
}
)
...
...
Could you provide your inspection info, please?
Thank you for quick response! It says correctly:
/* config.plugin('vue-i18n-feature-flags') */
new DefinePlugin(
{
__VUE_I18N_LEGACY_API__: 'false',
__VUE_I18N_FULL_INSTALL__: 'true',
__VUE_I18N_PROD_DEVTOOLS__: 'false'
}
),
but seems like it is not replaced on client side at compile? Anyway, this issue is seems not related to this plugin, therefore I close this issue.
Reporting a bug? If I enabled fullInstall in
vue.config.js
, then put theconsole.log(__VUE_I18N_FULL_INSTALL__)
invue-i18n.esm-bundler.js
, it will printsfalse
in console.Module versions (please complete the following information):
vue-cli-plugin-i18n
: 2.1.0To Reproduce Steps to reproduce the behavior: ex:
fullInstall: true
invue.config.js
v-t
directive with component.Expected behavior __VUE_I18N_FULL_INSTALL__ is set to
true
invue-i18n bundler