vue-clickaway
vue-clickaway copied to clipboard
Bugfix "Cannot read property 'context' of undefined` in update callback"
when update is called the vnode isn't passed and this results in an error. This commit fixes this. Would be glad if you would release this fix soon.
The bug was introduced with bfc451706280a390e95f4b94cba424f72f300599
@simplesmiler did you have a look on this one?
🙏 Running into this myself!
@simplesmiler is this project dead?
having the same problem with nuxt
Hello ! I have forked the project because i need this fix for my work. I will surely add your MR, so if you want, here it is :) : https://github.com/silverspectro/vue-clickaway
@silverspectro will you publish on npmjs.org?
sure, i can do that, but i can't use the same repo name as the first i think. So i don't know how to do that, as it would be cool to keep the same npm repo and just change the maintainers and github repo behind maybe ? @simplesmiler would it be ok for you ? Have you any intention to maintain this project further ? If not, i would be willing to do it (at least check the MR and do some code reviews). Do you have any ideas about this ?
@silverspectro you could fork it and publish with a different name
Hello!
Package published under a new very original name in npm: vue-clickaway2. Normally everything should work fine (tested on my project).
I did it a bit hastily so there may be some errors in the README or something still. Feel free to PR on it, I'll respond. Here is the new repo: https://github.com/silverspectro/vue-clickaway2
Hope it helps. Cheers,
I know this is a old thread, but I wanted to thank @joshiste and @silverspectro for doing this. Was running into a very specific bug, using clickaway with svgicon and the new repo fixed it perfectly.
Thank you very much.
Any news about this PR @simplesmiler ? That would be great to avoid multiply forks !
Ran into this issue today and can confirm that vue-clickaway2
works properly. Thanks @silverspectro <3
Just changed to vue-clickaway2
in our project due to this bug. Thanks a log for forking and publishing as a separate package!
@simplesmiler can you merge this in and redeploy to npm? If you need a new maintainer for the library, let me know.
I am also experiencing this on bind.