[Bug Report][3.5.17] [HMR] Cannot assign to read only property '_' of object '#' during hot-reload

[superCong]

Environment

Vuetify Version: 3.5.17
Vue Version: 3.4.25
Browsers: Chrome 123.0.0.0
OS: Windows

Steps to reproduce

{{a}} 4516

Expected Behavior

The webpage can be refreshed when saving

Actual Behavior

App.vue?t=1714120443791:106 TypeError: Cannot assign to read only property '_' of object '#'
at assign ()
at updateSlots (chunk-AZ23VQUG.js?v=ec09baeb:5952:9)
at updateComponentPreRender (chunk-AZ23VQUG.js?v=ec09baeb:7620:5)
at ReactiveEffect.componentUpdateFn [as fn] (chunk-AZ23VQUG.js?v=ec09baeb:7535:11)
at ReactiveEffect.run (chunk-AZ23VQUG.js?v=ec09baeb:434:19)
at instance.update (chunk-AZ23VQUG.js?v=ec09baeb:7602:17)
at updateComponent (chunk-AZ23VQUG.js?v=ec09baeb:7411:18)
at processComponent (chunk-AZ23VQUG.js?v=ec09baeb:7345:7)
at patch (chunk-AZ23VQUG.js?v=ec09baeb:6800:11)
at patchKeyedChildren (chunk-AZ23VQUG.js?v=ec09baeb:7755:9)
(anonymous) @ chunk-AZ23VQUG.js?v=ec09baeb:2015
(anonymous) @ App.vue?t=1714120443791:106
(anonymous) @ hmr.ts:77
(anonymous) @ hmr.ts:311
(anonymous) @ hmr.ts:277
queueUpdate @ hmr.ts:277
await in queueUpdate (async)
(anonymous) @ client.ts:205
handleMessage @ client.ts:203
(anonymous) @ client.ts:91
Show 8 more frames
Show less
App.vue?t=1714120443791:106 [HMR] Something went wrong during Vue component hot-reload. Full reload required.

Reproduction Link

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

[tyekx]

Hello, I am experiencing the same but on linux, just opened an empty project to test it, after adding a single v-nav-bar and v-nav-bar-title the error appeared.

Digging through, seems to be a vue issue, i made a comparison between a working repo and a new install. I found that reverting to vue@3.4.22 does fix this issue. Whereas npm list shows vue@3.4.25 from a fresh npm update.

[webarn]

I had the same problem

[superCong]

您好，我遇到了同样的情况，但在 linux 上，刚刚打开一个空项目进行测试，在添加单个 v-nav-bar 和 v-nav-bar-title 后出现错误。

深入研究，似乎是一个 vue 问题，我在工作存储库和新安装之间进行了比较。我发现恢复到确实可以解决这个问题。而 npm 列表显示来自新的 npm 更新。vue@3.4.22``vue@3.4.25

Yes, I also discovered it yesterday and the issue has been submitted to Vue

[superCong]

3.4.25

Using Vue 3.4.23 can solve the problem

I had the same problem

Using Vue 3.4.23 can solve the problem