ungap Modern Web development one jump at the time Photo by Denny Luan on Unsplash About The ungap project was born after years of attempts to always fix the same issue, but never in a modular way and, most importantly, never in a single, 100% code covered, organization. Focused on size, compatibility, and quality Each module is written in ES5 compatible syntax to avoid both unnecessary transpilers
The whatwg-fetch package is now a module with exports. The following methods/classes are available: fetch Headers Request Response DOMException All exports except for DOMException represent the polyfill implementations, not the native variants if they are available. This library still automatically acts like a polyfill if native window.fetch is unavailable; there is currently no way to use it as a
Polyfills are a valuable part of Web architecture, because they promote the adoption of new features during the implementation process. However, polyfills can also create problems for standardization efforts and therefore for the future of the Web. This document defines the risks, benefits, and role of polyfills on the Web, and proposes best practices for implementors, spec editors, website develo
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く