Packages: Update the note about using polyfill for ES2015+ features #34878
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gziolo
added
[Type] Developer Documentation
gziolo
requested review from
adamsilverstein,
adamziel,
ajitbohra,
atimmer,
cameronvoell,
chrisvanpatten,
dmsnell,
draganescu,
ellatrix,
getdave,
guarani,
kevin940726,
mmtr,
nerrad,
noisysocks,
swissspidy,
talldan and
tellthemachines
as code owners
7 tasks
ntsekouras
approved these changes
Sep 16, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Description
WordPress Core dropped support for IE 11 in the 5.8 release. At the same time we created a polyfill to ES2015+ features that better reflects the needs of the WordPress ecosystem knowing exactly the target supported browsers. Let's update README files in all packages to recommend the custom polypill that WordPress Core is using.
I see that Visual Studio Code triggered Prettier run on all modified files, but that can be ignored. We don't validate the file formatting in markdown files yet, so this is something that still happens from time to time.
Props to @ciampo for the copy update when improving the README file in
@wordpress/components.