Polyfills as a Service
polyfills.io
Polyfills as a Service
1–10 of 17 posts
Re: Polyfills as a Service
#2Getting an Internal Server Error at https://cdn.jsdelivr.net/polyfills/polyfill.js
Re: Polyfills as a Service
#3> To include polyfills, use a -, otherwise, use a +.
That should say 'exclude', right? To avoid confusion, probably avoid "otherwise" too, spell it out "to exclude polyfills use a `-`; to include only listed polyfills use a `+`"
Re: Polyfills as a Service
#4This is a really neat idea... when paired with the Express middleware and Babel, you could have a pretty clean ES6 app with modern browser features and still have it work on older browsers.
Re: Polyfills as a Service
#5This 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.
Re: Polyfills as a Service
#6This 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.
The problem is their origin not the CDN itself. The author is not responding and wont fix the server
Re: Polyfills as a Service
#7This is a really neat idea... when paired with the Express middleware and Babel, you could have a pretty clean ES6 app with modern browser features and still have it work on older browsers.
You don't need this if you write your app with babel. it will automatically add polyfills if needed.
Re: Polyfills as a Service
#8Author 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
#9This is a really neat idea... when paired with the Express middleware and Babel, you could have a pretty clean ES6 app with modern browser features and still have it work on older browsers.
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 in many modern browsers, but not all.
Re: Polyfills as a Service
#10If this interests you, there is also https://cdn.polyfill.io/v1/docs/ (https://github.com/Financial-Times/polyfill-service), backed by FT.