search

szboynono / mosha-vue-toastify

A light weight and fun Vue 3 toast or notification or snack bar or however you wanna call it library.
https://szboynono.github.io/mosha-vue-toastify/
MIT License
222 stars 15 forks source link

[Vue3 + Vite] Uncaught TypeError: can't access property "innerWidth", o4.currentTarget is null #13

Closed dzikoysk closed 3 years ago

dzikoysk commented 3 years ago

From time to time when I create toast in my component with this code:

setup() {
    const signin = (alias, token) => {
      client.auth.me(alias, token) // <-- Axios call
        .then(_ => createToast(`Dashboard accessed as ${alias}`, { position: 'bottom-right' }))
        // [...]
     }
}

I'm getting this exception in console:

15:14:31.517 Uncaught TypeError: can't access property "innerWidth", o4.currentTarget is null
    o3 mosha-vue-toastify.es.js:1
    o2 mosha-vue-toastify.es.js:1
    setTimeout handler*E/< mosha-vue-toastify.es.js:1
    EventListener.handleEvent* mosha-vue-toastify.es.js:1
    callWithErrorHandling runtime-core.esm-bundler.js:6990
    callWithAsyncErrorHandling runtime-core.esm-bundler.js:6999
    __weh runtime-core.esm-bundler.js:2270
    flushPostFlushCbs runtime-core.esm-bundler.js:7191
    render2 runtime-core.esm-bundler.js:5142
    render runtime-dom.esm-bundler.js:1489
    Z mosha-vue-toastify.es.js:1
    Q mosha-vue-toastify.es.js:1
    signin LoginModal.vue:52
    promise callback*signin LoginModal.vue:52
    3 LoginModal.vue:16
    callWithErrorHandling runtime-core.esm-bundler.js:6990
    callWithAsyncErrorHandling runtime-core.esm-bundler.js:6999
    invoker runtime-dom.esm-bundler.js:347
    addEventListener runtime-dom.esm-bundler.js:297
    patchEvent runtime-dom.esm-bundler.js:315
    patchProp runtime-dom.esm-bundler.js:379
    mountElement runtime-core.esm-bundler.js:4105
    processElement runtime-core.esm-bundler.js:4068
    patch runtime-core.esm-bundler.js:3988
    mountChildren runtime-core.esm-bundler.js:4187
    mountElement runtime-core.esm-bundler.js:4096
    processElement runtime-core.esm-bundler.js:4068
    patch runtime-core.esm-bundler.js:3988
    mountChildren runtime-core.esm-bundler.js:4187
    mountElement runtime-core.esm-bundler.js:4096
    processElement runtime-core.esm-bundler.js:4068
    patch runtime-core.esm-bundler.js:3988
    mountChildren runtime-core.esm-bundler.js:4187
    processFragment runtime-core.esm-bundler.js:4355
    patch runtime-core.esm-bundler.js:3984
    mountChildren runtime-core.esm-bundler.js:4187
    mountElement runtime-core.esm-bundler.js:4096
    processElement runtime-core.esm-bundler.js:4068
    patch runtime-core.esm-bundler.js:3988
    mountChildren runtime-core.esm-bundler.js:4187
    mountElement runtime-core.esm-bundler.js:4096
    processElement runtime-core.esm-bundler.js:4068
    patch runtime-core.esm-bundler.js:3988
    componentUpdateFn runtime-core.esm-bundler.js:4536
    run reactivity.esm-bundler.js:160
    setupRenderEffect runtime-core.esm-bundler.js:4655
    mountComponent runtime-core.esm-bundler.js:4438

It's quite random, but it happens when the toast disappears.

szboynono commented 3 years ago

Hey, thanks for the feedback, can you try out v1.0.20? I made a little fix in it and hope it fixes the issue.

dzikoysk commented 3 years ago

Just bumped to 1.0.20 and for now I don't see these errors, so in fact I guess it's fixed. Thanks for quick response and hotfix :)