this looks dangerous to me. we did this once, and vues reactivity system eventually proxies the entire system including the dom because it climbs through the accessor nodes: node > parent > … > renderer > domElement > parent > … > document.body which is the biggest performance impact you can possibly have since three updates 60 times per second, triggering thousands of unintentional proxies. you can’t make three “reactive” by proxying its internals, you should drive it with reactive props instead.