Cannot read property '__disableEmitter'

[thisisablock]

vue & vue-i18n version

• vue: 3.0.0
• vue-i18n: 9.0.0-beta.4

What is actually happening?

On Beta 4 i get on a page change with [email protected] an error

vueI18n.__disableEmitter && _vueI18n.__disableEmitter();

it related to

      _vueI18n.__disableEmitter && _vueI18n.__disableEmitter();

On Beta 3 everything works fine

[kazupon]

I could not reproduce my environments ... 😞
Could you provide minimum reproduction codes please?

[kazupon]

close due to in-activity

[holtwick]

I encounter the same problem with version 9.0.0. My projects use latest vite, vue3, vue-router and typescript. Everything worked fine until today. It is only triggered in certain circumstances for special routes. But it disappears if I don't use i18n.

        beforeUnmount() {
            const instance = getCurrentInstance();
            /* istanbul ignore if */
            if (!instance) {
                throw createI18nError(22 /* UNEXPECTED_ERROR */);
            }
            /* istanbul ignore if */
            if (((process.env.NODE_ENV !== 'production') || __INTLIFY_PROD_DEVTOOLS__) && !false) {
                if (this.__emitter) {
                    this.__emitter.off('*', addTimelineEvent);
                    delete this.__emitter;
                }
                const _vueI18n = this.$i18n;
                _vueI18n.__disableEmitter && _vueI18n.__disableEmitter();
                delete this.$el.__INTLIFY__;
            }
            delete this.$t;
            delete this.$tc;
            delete this.$te;
            delete this.$d;
            delete this.$n;
            delete this.$tm;
            i18n.__deleteInstance(instance);
            delete this.$i18n;
        }

[holtwick]

It somehow seems to end up in the wrong context. The contents of this look like the properties of a component I use:

[holtwick]

Ok, the pages that cause issues use <teleport>. It works if I remove it. I consider this being a bug in either vue3 or i18n. What do you think @kazupon ? Worth reopening the ticket?

[holtwick]

This seems to be related to a vue bug, in vue 3.0.7 everything works fine again.