vue-i18n-next: TypeError: Cannot read properties of undefined (reading '__composer')
Reporting a bug?
Follow up for https://github.com/intlify/vue-i18n-next/issues/793#issuecomment-1015856474
I’m hitting a slightly similar error to #793 with the latest version 9.2.0-beta.28:
I could not notice if it has any effects on the UI of my application but the errors are really annoying.
The code section (copied from dev tools):
mounted() {
nextTick(() => {
/* istanbul ignore if */
if (((process.env.NODE_ENV !== 'production') || __VUE_PROD_DEVTOOLS__) &&
!false &&
this.$el) {
this.$el.__VUE_I18N__ = this.$i18n.__composer;
const emitter = (this.__v_emitter =
createEmitter());
const _vueI18n = this.$i18n;
_vueI18n.__enableEmitter && _vueI18n.__enableEmitter(emitter);
emitter.on('*', addTimelineEvent);
}
});
},
Expected behavior
No error in console.
Reproduction
This isn’t a minimal reproduction of the bug, but I’m not sure how I should reproduce it - even in my application I can’t understand why it happens and it does not happen all the time.
- Check out https://kolaente.dev/vikunja/frontend at commit
55b77725df4a71ea248fbee2eb7b613fc590f6aa
- Install dependencies with
yarn install
- Start the dev server with
yarn serve
- Using chrome, open the app at
localhost:5000
- As an api url, use
https://try.vikunja.io
- Use
demo
as a username and password. - Click around in the app a bit with dev tools openend, the error will appear eventually.
System Info
System:
OS: Linux 5.10 NixOS 21.11 (Porcupine) 21.11 (Porcupine)
CPU: (12) x64 AMD Ryzen 5 3600 6-Core Processor
Memory: 12.41 GB / 31.37 GB
Container: Yes
Shell: 5.8 - /run/current-system/sw/bin/zsh
Binaries:
Node: 14.18.1 - /etc/profiles/per-user/konrad/bin/node
Yarn: 1.22.17 - /etc/profiles/per-user/konrad/bin/yarn
npm: 6.14.15 - /etc/profiles/per-user/konrad/bin/npm
Browsers:
Chromium: 97.0.4692.71
Firefox: 95.0.2
npmPackages:
@vitejs/plugin-legacy: 1.6.4 => 1.6.4
@vitejs/plugin-vue: 2.1.0 => 2.1.0
@vue/compat: 3.2.28 => 3.2.28
@vue/eslint-config-typescript: 10.0.0 => 10.0.0
vite: 2.7.13 => 2.7.13
vite-plugin-pwa: 0.11.13 => 0.11.13
vite-svg-loader: 3.1.2 => 3.1.2
vitest: 0.1.27 => 0.1.27
vue: 3.2.28 => 3.2.28
vue-advanced-cropper: 2.7.1 => 2.7.1
vue-drag-resize: 2.0.3 => 2.0.3
vue-flatpickr-component: 9.0.5 => 9.0.5
vue-i18n: 9.2.0-beta.28 => 9.2.0-beta.28
vue-router: 4.0.12 => 4.0.12
vue-tsc: 0.30.6 => 0.30.6
vuedraggable: 4.1.0 => 4.1.0
vuex: 4.0.2 => 4.0.2
Screenshot
No response
Additional context
No response
Validations
- Read the Contributing Guidelines
- Read the Documentation
- Check that there isn’t already an issue that reports the same bug to avoid creating a duplicate.
- Check that this is a concrete bug. For Q&A open a GitHub Discussion
- The provided reproduction is a minimal reproducible example of the bug.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 2
- Comments: 18 (7 by maintainers)
Hi! Same problem with 9.1.10 (also tried 9.1.9 and 9.1.8). Not happening with 9.2.0-beta.36.
Any chance for a fix in 9.1.x or a non-beta version?
Thanks!
@kazupon I just tried it with v9.2-beta.30 and now it’s working with no errors.