vuetifyjs / vuetify

🐉 Vue Component Framework
https://vuetifyjs.com
MIT License
39.72k stars 6.95k forks source link

[Bug Report][3.6.1] TypeError: Cannot convert object to primitive value #19733

Closed toughlex-donatas closed 2 months ago

toughlex-donatas commented 5 months ago

Environment

Vuetify Version: 3.6.1 Vue Version: 3.4.24 Browsers: Chrome 124.0.0.0 OS: Linux

Steps to reproduce

Just run reproduction snippet and get runtime error.

Expected Behavior

Don't get runtime error

Actual Behavior

Get runtime error "TypeError: Cannot convert object to primitive value".

Reproduction Link

https://play.vuetifyjs.com/#...

For some reason it mostly works on play.vuetifyjs.com (I reproduced the error few times), but stably fails on my machine.

Other comments

Error occurs, when MaybeTransition receives props.target = Proxy(Array) [ VueComponent ] instead of HTML element from VOverlay. I don't have problems with Vue 3.4.23.

habibalkhabbaz commented 5 months ago

Same. The issue appeared after upgrading Vue to v3.4.24 (and above). Downgrading to v3.4.23 solves the issue for now.

image

https://play.vuetifyjs.com/#eNqdVE2PmzAQ/SsjethWwomSTT8UZSP10EOlHnvb7MGAs7VibMseSLeI/94xBrKwiSrVJzzz5s3XM49N4l2+/Grtoq5Esk12KEqrOIr9QQPsaoY88+EToGalKYR6OCRkOyTRmBtlHJkyVQn27MQLK7g7Cc02A+LZmXOPFRqFYzxHWYto8r/MmXFHkC5Jl3RIC9uaEyuRrw5J7+l8MjcaPHKH+7KQLDPmVFLS3TK6RuhP4lj1jOQjyhv86//nX7/l7789XfoZnqUuzHk+wEsx0c8kzX7adGyBhkyD09gxv8L+g2DWlZIex/toiTE1O3ZblGCO8LhKYZ3CfQqbFD6m8CmFzyl8eToksD2JlwB7xRzODyKC74GoaUBC28bOx1SDpuAdt1boYhIc12GMQmlBmZyjNDooyiCacpZpThekxLGrvQHrjPXQXgnpcmQ4qWo4YaUUHjbN89xUGpkoJA7ynZ6aO8k1hhWK3zcwXv4J4/clV+oGC8toYYTpKr6G2YdVU8Fvm19OHujE5S3Xe/hGxROsu8zmHIQZBz3xXOUM4FEgFx311kF6VwR5sdF1Qk1XnztpEbzAKtYgS2scQgNOHKGFozMl3NGv6C5KiHZD0gqP9SEg3q8+BM7IQvFJmyb3i81ivUlSXSn19BecaWbb

And as mentioned by @toughlex-donatas - I don't know why it is not always reproduceable on VPlay however on our local machines or when we run npm run prod, the issue is always there

jmeij commented 4 months ago

Had this issue also. Removing my node_modules locally and running npm ci after fixed it for me.

KaelWD commented 2 months ago

Duplicate of #19685