search

Agontuk / vue-cropperjs

A Vue wrapper component for cropperjs https://github.com/fengyuanchen/cropperjs
MIT License
937 stars 224 forks source link

'$attrs is readonly' and '$listeners is readonly' #26

Closed piligrimnick closed 5 years ago

piligrimnick commented 7 years ago

I think it's a problem with Vue 2.4.4 check this issue - looks the same https://github.com/apertureless/vue-chartjs/issues/151

Agontuk commented 7 years ago

Thanks for the report, I'll check it as soon as I can.

Agontuk commented 7 years ago

I tested my example project with 2.4.4 but found no issue. Can you explain how to reproduce it ?

Agontuk commented 6 years ago

Closing due to inactivity.

beliolfa commented 6 years ago

I am getting this error too. Is there a fix?

Agontuk commented 6 years ago

please provide an example on how to reproduce this.

beliolfa commented 6 years ago

I will try to make a reproduction soon. But this is happening to me developing a plugin for another package.

https://github.com/64robots/nova-image-cropper

Maybe its because of duplication of Vue instances but I can't figure out the solution.

mnooblet commented 6 years ago

I'm facing the same issue, using vue cropper in my component and trying to change a data value in the same component I get this error.

Vue version 2.5.16

BTW if anyone else is getting this error I solved it by wrapping the cropper in it's own .vue file, kinda anoying to proxy everything but at least it's working without the warning.

san-kumar commented 5 years ago

I'm facing the same issue, using vue cropper in my component and trying to change a data value in the same component I get this error.

Vue version 2.5.16

BTW if anyone else is getting this error I solved it by wrapping the cropper in it's own .vue file, kinda anoying to proxy everything but at least it's working without the warning.

Yes, it worked! Thanks :)

beliolfa commented 5 years ago

Wrapping in its own component is not working for me. Any help?

Agontuk commented 5 years ago

I'm re-opening this, please provide a sample project so that I can debug the issue.

beliolfa commented 5 years ago

Ive created a repo and I cant reproduce it. I think its because of the Vue.extend you have.

Im using this in a Laravel Nova package, and I believe your package is using the Vue instance from Nova, which causes this kind of warnings.

Im going to fork this repo and try to not using Vue.extend and see what happens

beliolfa commented 5 years ago

I fixed this issue in my project with this PR #40. Hope it helps!

Agontuk commented 5 years ago

Thanks, I'll check it out asap.

buwilliams commented 5 years ago

+1 We are waiting on this PR as well.