Error Events.emit is not a function
See original GitHub issueOn version 0.14.0 using Vue 2 with TypeScript and composition API, when leaving component that uses vue-masonary gets the following error:
vue.runtime.esm.js?2b0e:619 [Vue warn]: Error in directive masonry unbind hook: "TypeError: Events.emit is not a function"
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:13 (7 by maintainers)
Top Results From Across the Web
Vue js : _this.$emit is not a function - Stack Overflow
This error surfaces if $emit is not on the current context/reference of this , perhaps when you're in the then or catch methods...
Read more >Event.$emit is not a function when trying to emit within a ...
I'm trying to emit an event from within a component and listen to the event on another component. I'm using Laravel 5.3 and...
Read more >Uncaught TypeError: app.$emit is not a function - Laracasts
I am using a component that uploads images using Dropzone and once the upload finishes, it should emit an event so that I...
Read more >Angular: .emit is not a function · Discussion #16507 - GitHub
Hello,. I have created stories from a library of angular components, but in all I have the same error with the Output events....
Read more >events.EventEmitter.emit JavaScript and Node.js code examples
How to use. emit. function ... EventEmitter.emit(Showing top 15 results out of 1,062) ... invokeCallback(cb, new Error('application is not running now.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@rosenfeldalon published 0.14.1 just now - https://www.npmjs.com/package/vue-masonry
please upgrade and give it a try
Is this fixed in version 0.14.0 ? I still see this error. Thanks in advance