Uncaught (in promise) TypeError: Cannot read property '__disableEmitter' of undefined

[mits87]

Hi,

I've just installed the latest version of vue-i18n-next and I have a big problem because it does it work correctly with vue-router. Exactly the same bug like we can find here: #253

Some people suggested to use NODE_ENV=production but I can't do that based on fact I'm using different .env files for different environments. Also based on NODE_ENV I'm attaching some extra functionality. So this is not solution.

Version & libraries:
I'm using these version of libraries:

"dependencies": {
    "@vueuse/core": "^4.6.2",
    "core-js": "^3.9.1",
    "register-service-worker": "^1.7.2",
    "vue": "^3.0.2",
    "vue-i18n": "^9.0.0",
    "vue-router": "^4.0.5",
    "vuex": "^4.0.0"
  },

The behaviour:
When I'm trying to change page (using vue-router) I get those errors:

vue-i18n.esm-bundler.js?47e2:1672 Uncaught (in promise) TypeError: Cannot read property '__disableEmitter' of undefined
    at Proxy.beforeUnmount (vue-i18n.esm-bundler.js?47e2:1672)
    at callWithErrorHandling (runtime-core.esm-bundler.js?5c40:154)
    at callWithAsyncErrorHandling (runtime-core.esm-bundler.js?5c40:163)
    at Array.hook.__weh.hook.__weh (runtime-core.esm-bundler.js?5c40:1957)
    at invokeArrayFns (shared.esm-bundler.js?9ff4:470)
    at unmountComponent (runtime-core.esm-bundler.js?5c40:4819)
    at unmount (runtime-core.esm-bundler.js?5c40:4731)
    at Object.remove (runtime-core.esm-bundler.js?5c40:5125)
    at unmount (runtime-core.esm-bundler.js?5c40:4755)
    at unmountChildren (runtime-core.esm-bundler.js?5c40:4859)

Someone has still a similar problem?

[kazupon]

Thank you for your reporting!

I tried to reproduce this issue.
Unfortunately, I could not reproduce...

The below issue minimul repo:
https://github.com/kazupon/vue-i18n-next-issue-412

I need the component structure information from the App root and the following information for each component to solve this problem.

• whether use i18n custom block
• or, whether use i18n options
• or, not use both

Could you give us the component info and structure, please? 🙏

[jiangjunfeng98]

vue 3.0.7 is work

"vue": "3.0.7",
"vue-i18n": "^9.0.0"

[ota-meshi]

Are you using <teleport>?
If so, it may be related to a bug in vue v3.0.9.
vuejs/core#3497

There is no $i18n property on the second call of beforeUnmount.

[holtwick]

Oh, @ota-meshi and @jiangjunfeng98 why didn't i see your comments earlier, it could have saved my morning ;) I came to the same conclusions. Vue 3.0.7 works and it is related to <teleport>. See my debug comment here: #133

[mits87]

@ota-meshi and @jiangjunfeng98 Yes, I'm using <teleport> in my project and I changed my VUE version to vue 3.0.7 but the problem still exists there 👎

In a few hours I will try to prepare some sandbox version of that problem.

[holtwick]

@mits87 did you check which version is really installed using npm ls vue? Often it is not corresponding to the one in package.json. Try npm i [email protected] to force update.

[mits87]

ohh, you are right. The npm ls vue still displayed 3.0.9.
So it means we are waiting for bug fix from here vuejs/core#3497

[shqyking]

I encountered same problem and my Vue version is 3.0.7(double checked with npm ls vue). I didn't use <teleport> anywhere in the codebase, but maybe some library that I use is using the <teleport>. kazupon/vue-i18n#1168 above is opened by me.

[ota-meshi]

It works fine with the newly released vue v3.0.10.

[antonio-wundermart]

We have the same issue, in particular we are using this stack:

• vite,
• vue3,
• primevue (ui framework)
• vue-i18n.

In the latest versions of Primevue they use heavily teleports, which cause the aforementioned error when we change route.
We solved downgrading primevue to an older version which doesn't rely on teleport, but this is not optimal at all. We are considering to move out from vue-i18n since we want also to start using teleport as well for our components.

[ota-meshi]

You need to use [email protected] or later.

[antonio-wundermart]

You need to use [email protected] or later.

Thanks, you are right, I cannot replicate it anymore after upgraded vue and cleaned my caches.

[kazupon]

This issue was caused by a bug in Vue. This problem does not occur after [email protected], so it is closed.

Thank you for your feedback!

[ldsenow]

I am on Vue 3.2.25, however, the issue is still happening.