This is a really great example of why not to use random CDN's just because it is convenient. Currently they are just serving internal server errors.
Polyfills as a Service
11–17 of 17 posts
Re: Polyfills as a Service
#12If this interests you, there is also https://cdn.polyfill.io/v1/docs/ ( https://github.com/Financial-Times/polyfill-service ), backed by FT.
Works like a charm
Re: Polyfills as a Service
#13Earlier quoted context omitted.
You don't need this if you write your app with babel. it will automatically add polyfills if needed.
No, the point of this tool is that some browsers require a polyfill, and some don't because the feature is natively supported. A transpiler like Babel cannot possibly determine that, so it has to be safe and include polyfills for all features used in the code it's transpiling, reglardless of whether or not the browser you're using already supports the feature. A good example of this is Promises, which are supported i…
If you're using webpack you can use the code splitting feature to make sure the browser doesn't download that extra few KBs (which is presumable a trade-off between (an) extra roundtrip(s), so maybe you should just swallow those KBs).
Re: Polyfills as a Service
#14Author here. Haven't maintained this in a while. It's down due to some breaking changes in libraries and I haven't updated the code to handle it. I also stopped using this as you could just use babel to automatically use whichever polyfill you use with babel-runtime. Saving a few kb is an overoptimization. If you're interested in maintaining this project, let me know. I can add you to the GitHub organization.
Re: Polyfills as a Service
#15Re: Polyfills as a Service
#16this is why web development makes me feel bad... all this time an effort spent solve very easily and classically well solved problems in the browser, because browsers are wastelands of terrible engineering :I
Re: Polyfills as a Service
#17Author here. Haven't maintained this in a while. It's down due to some breaking changes in libraries and I haven't updated the code to handle it. I also stopped using this as you could just use babel to automatically use whichever polyfill you use with babel-runtime. Saving a few kb is an overoptimization. If you're interested in maintaining this project, let me know. I can add you to the GitHub organization.
Would be nice to have a note on the homepage indicating that this project has since been abandoned.