Your new post is loading...
When you use reusable components (whether through convention, a framework like Fruit Machine or React, or directly using the emerging Web Components standard), you might find that components ship with polyfills. Your page may end up containing multiple polyfills for the same feature. You might also find that these polyfills all use slightly different implementations, and it’s not immediately obvious which is a faithful emulation of the missing feature. Even the packaging format and file structure is likely to vary between polyfills and make each one a special case.
This is far from ideal. We need some way of polyfilling browsers that avoids this duplication.
