3 ms·
https://caniuse.com/#feat=proxy https://caniuse.com/#feat=proxy Seems to have a decent coverage for most users
by isuckatcoding 8y ago
https://caniuse.com/#feat=proxy https://caniuse.com/#feat=proxy
Seems to have a decent coverage for most users
- throwaway2016a 8y agoThe issue is that for many applications anything less than ~98% is not acceptable (eCommerce for instance). This is 87% (to save people a click). And because this works on fundamental operators, a polypill is impossible. However, if you are using Babel to transpile your JS or using Node.js this seems like it could be very useful.
- franciscop 8y agoYou also cannot transpile Proxies, since they do not have an equivalent in "old javascript" as they are a feature in such a level that cannot be built with previous tech.
- throwaway2016a 8y agoYou can transpile pretty much anything. The transpiler doesn't have to just modify the declaration, it can also modify the calls... https://www.npmjs.com/package/babel-plugin-proxy https://www.npmjs.com/package/babel-plugin-proxy > they do not have an equivalent in "old javascript" Sure they do. Function calls.
- franciscop 8y agoAh totally, I misspoke. I was talking from the point of view of a library author, where I'd like to transpile my code so anyone can include the library and use it. In the same way I can use const, transpile my code and no one worries about me using const internally, the same cannot be said for Proxy. So, between everyone having to transpile their client code or losing the few devs who need to support IE, I prefer the latter for my projects.