Closed douira closed 1 year ago
A follow up on this issue: Vue Devtools seems to be checking for properties on the store object through some mechanism and this generates hundreds of warnings in the console like this:
doc.ts:48 property not found on root doc render
getYjsByTypeDescription @ doc.ts:48
get2 @ doc.ts:101
(anonymous) @ backend.js:6007
processSetupState @ backend.js:6001
getInstanceState @ backend.js:5917
getInstanceDetails @ backend.js:5909
(anonymous) @ backend.js:6977
callHandlers @ backend.js:746
callHook @ backend.js:227
inspectComponent @ backend.js:316
sendSelectedComponentData @ backend.js:1528
await in sendSelectedComponentData (async)
(anonymous) @ backend.js:2315
wrappedListener @ backend.js:7211
emit @ backend.js:10850
_emit @ backend.js:7259
(anonymous) @ backend.js:7197
(anonymous) @ backend.js:7197
listener @ backend.js:14480
postMessage (async)
n @ proxy.js:1
backend.js
appears to be part of Vue Devtools. The other properties it warns abut include render
, __asyncLoader
, __v_isReactive
, effect
, state
, _
, currentRoute
.
The warning
doc.ts:46 property not found on root doc __v_isRef
and similar warnings about other internal Vue properties are spammed on the console. In certain situations, it also prints properties that I'm working with myself as a warning. It would be good if this library could filter out these warnings for internal Vue properties as there doesn't seem to be a way around it. The Vue3 examples in the documentation also have this issue with the warnings.