Vuex v3.1.2 warns when informing an existing module

[davidpelayo]

Due to this at Vuex v3.1.2, we now get a warning when initialising the usage of the vuex-i18n plugin informing a third parameter, config, containing a specific moduleName.

Within my SPA bootstrapping process, I'm declaring a module named I18nModule with my own state keys and everything, which I then later reuse to inject the managed-by-vue-i18n-translations, to avoid having two different modules for the same purpose.

I'm wondering why instead of reusing the existing one a new one is being created here, leading to the warning.

Any idea on this regard? Help is appreciated. Thanks.

[kazupon]

Thank fou you for the feedback!

vue-i18n does not have a module and namespace.
about vuex-i18n, you can access the here.
https://github.com/dkfbasel/vuex-i18n