UI: Move the text encoding polyfill to a a proper detecting polyfill #4767
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I spotted a huge bump in the size of my built output from a few weeks ago:
I followed it back to #4613 which was to add a different TextEncoder polyfill, but this wasn't exactly polyfilled. Even though certain browsers didn't need the polyfill, the polyfill was still in the bundled vendor.js file.
This PR splits this out into a proper polyfill. The TextEncoder polyfill is now only requested/downloaded if the browser you are using a browser that doesn't have a native implementation (basically IE).
Overall this puts my vendor.js file back to the size it was previously.