You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -795,7 +795,7 @@ For example, if lazy loading `<script type="module-shim">` scripts alongside sta
795
795
796
796
DOM `load` events are fired for all `"module-shim"` scripts both for success and failure just like for native module scripts.
797
797
798
-
### Pollyfill Enable Option
798
+
### Polyfill Enable Option
799
799
800
800
The `polyfillEnable` option allows enabling polyfill features which are newer and would otherwise result in unnecessary polyfilling in modern browsers that haven't yet updated.
801
801
@@ -813,7 +813,7 @@ In adddition, the `"all"` option will enable all features.
813
813
814
814
The reason the `polyfillEnable` option is needed is because ES Module Shims implements a performance optimization where if a browser supports modern modules features to an expected baseline of import maps support, it will skip all polyfill source analysis resulting in full native passthrough performance.
815
815
816
-
### Pollyfill Disable Option
816
+
### Polyfill Disable Option
817
817
818
818
Conversely to `polyfillEnable` it can be beneficial to dissable unused features where excluding those features from the baseline allows avoiding unnecessary feature detections or unnecessary analysis of module graphs.
0 commit comments