You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When updating vue-loader to version 16.6.0 the <i18n> blocks within SFC is not respected anymore in Webpack production builds. The issue cannot be seen in dev builds.
This means that local translations within SFC are not working and the translation key is shown instead.
Downgrading to vue-loader version 16.5.0 fixes the issue again.
Reporting a bug?
When updating
vue-loader
to version 16.6.0 the<i18n>
blocks within SFC is not respected anymore in Webpackproduction
builds. The issue cannot be seen indev
builds.This means that local translations within SFC are not working and the translation key is shown instead.
Downgrading to
vue-loader
version 16.5.0 fixes the issue again.Possible cause: vuejs/vue-loader@11e3cb8
Is this something which must be fixed in
vue-i18n
?Expected behavior
The
<i18n>
block of a SFC should continue to work just like before.Reproduction
Have a SFC with a
<i18n>
block, update tovue-loader
16.6.0or newer and do a Webpack
production` build. The translations are ignored.test.js
:components/Test.vue
:test.js
compiled withdev
:test.<hash>.js
compiled withprod
andvue-loader
16.6.0/16.7.0:test.<hash>.js
compiled withprod
andvue-loader
16.5.0:System Info
Screenshot
Before (labels translated):
After (labels untranslated):
Additional context
No response
Validations
The text was updated successfully, but these errors were encountered: