The "shims for IE" (though they're not just for IE as indicated in #411) are rather large; could we require smaller shims? If someone is using full ES6 they'll need them anyway but for people relying on native ES5 this will be a big barrier to adopt the new Component Router.
I think we should identify what we really need and provide our own, smaller shim. If someone is already including the full ones they'd not need the smaller one but for others it will be useful.
Also, I think we should explore shimming the ES6 promise using our $q service so that we don't need the Promise polyfill at all.
mgol
commented
8 years ago
The "shims for IE" (though they're not just for IE as indicated in #411) are rather large; could we require smaller shims? If someone is using full ES6 they'll need them anyway but for people relying on native ES5 this will be a big barrier to adopt the new Component Router.
I think we should identify what we really need and provide our own, smaller shim. If someone is already including the full ones they'd not need the smaller one but for others it will be useful.
Also, I think we should explore shimming the ES6 promise using our
$qservice so that we don't need the Promise polyfill at all.