Compatibility build: How do we replace the component proxy's functionality? about core HOT 5 CLOSED

@LinusBorg we will fallback to actually defining everything on the instance, but only when we detect the runtime doesn't support native Proxies. That logic will live in runtime-core and be included/excluded via a build time flag.

from core.

As a sidenote, I realized that we also use WeakMaps in a couple of places outside of the observer package.

Since WeakMap can't be properly polyfilled(?), should we choose a different implementation or am I missing something`

from core.

core-js has a built-in WeakMap polyfill: https://github.com/zloirock/core-js/blob/master/packages/core-js/modules/es.weak-map.js

from core.

I see. I'm a little suprised (positively!) that this behaviour can in fact be polyfilled, good to know.

So we would require some polyfills for the compatibility build, for Set, Map, WeakMap etc. Seems fair in order to drag ppl into the future :-P.

from core.

Great.

from core.