v-img throws error: "TypeError: Cannot read properties of undefined (reading 'observer') at unbind"

[M-Barari]

Nuxt.js 2.15.8
@nuxtjs/vuetify 1.12.1

my app was working just fine until yesterday that i ran npm i . after that on page change i was getting this error:

client.js?06a0:103 TypeError: Cannot read properties of undefined (reading 'observer')
    at unbind (index.ts?8358:63)
    at callHook$1 (vue.runtime.esm.js?2b0e:6724)
    at _update (vue.runtime.esm.js?2b0e:6685)
    at updateDirectives (vue.runtime.esm.js?2b0e:6626)
    at Array.unbindDirectives (vue.runtime.esm.js?2b0e:6620)
    at invokeDestroyHook (vue.runtime.esm.js?2b0e:6159)
    at VueComponent.patch [as __patch__] (vue.runtime.esm.js?2b0e:6511)
    at VueComponent.Vue.$destroy (vue.runtime.esm.js?2b0e:4016)
    at destroy (vue.runtime.esm.js?2b0e:3178)
    at invokeDestroyHook (vue.runtime.esm.js?2b0e:6158)

I disabled my packages one by one until found the culprit !! Vuetify: "^2.5.5" . so changed to Vuetify: "2.5.5" and problem solved so removed the package for other possible issues.
Now I get the issue on one of my components on this line of code:

<v-img class="product_img" contain :alt="product.title" :src="imageUrl" />

by changing that to :

<img class="product_img" :alt="product.title" :src="imageUrl" />

the problem was solved ! so what exactly is the origin of this issue??

P.S. : It's no relevant but would be happy to know; My app was working perfectly by @nuxtjs/vuetify module alone but recently when I created a new nuxt project it was using Vuetify too beside @nuxtjs/vuetify . so what is the benefits ? is it necessary ?

[enigmafan]

I just had a similar issue and ended up here. I solved it by using version 2.6.0 of Vuetify.