Proxies cannot be transpiled or polyfilled due to Proxies Proxies Proxies cannot be written in ES5 (Proxies cannot be transpiled or polyfilled)
background
Vue 3 (vue 3)
BOSS: Which project in our team is using Vue 3?
Team leader A: We used Vue 3 for the micro front-end main project (look at that, how advanced my team is)
Vue 3 does not support IE 11.
.
My question
Vue 3 does not support IE11, compatibility issues? Polyfill should be able to deal with misalignment and compatibility problems.
I wanted to ask in the group, but I was the lowest ranking person in the group. The group of group C asked, and the group leader C (my group leader) replied:
Do not support IE is the result, to analyze the cause can not “hold fruit cable” – general arbitrary attribution out of the inaccurate.
To understand why, read the RFC and the discussion
I suspect he’s being clever, but he’s not.
Internet Explorer 11 is not supported
So I brave to read English, summed up three reasons:
- Proxy smells better and the Vue team wants to use it
- The Vue team wants to play a part in killing IE
- If supported, development and maintenance costs are too high.
Vue 2 is based on ES5 getters /setters, and Vue 3 is based on proxies, which require logical double-write to implement. The Vue team doesn’t want to make more sacrifices for IE11, and it will be difficult for me if a Super Proxy comes out in the future.
Babel?
So again, the Proxy problem is Babel Polyfill?
Babel… I don’t care about that question
from babel
Unsupported feature
Due to the limitations of ES5, Proxies cannot be transpiled or polyfilled. See support in various JavaScript engines.
Finally, I found the root cause:
Transpiled and Polyfilled Babel does not support Proxy features. ES6 is the afterwave of ES5, not the trouble.
There are things in the JS world that Babel can’t handle.
Proxies cannot be transpiled or polyfilled due to the Proxies Proxies Proxies cannot be transpiled or polyfilled
Yuxi: Vue3 is considering ditching Internet Explorer altogether