build(js,css): add browserslist spec and update JS and CSS toolchains #4083
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.
overview
Following up on our cross-browser support discussion(s), this PR implements JS polyfilling and improves out CSS polyfilling support
DO NOT MERGE until after PD's next releasePD release, merge unblockedchangelog
.browserslistrc
file to specify our JS and CSS polyfill support@babel/preset-env
polyfilling via core-js to our three main web-apps (app, PD, LL)color
function renamed tocolor-mod
review requests
This is marked as do not merge until the planned bugfix release of PD goes out at the end of this week. Everything looks good in my cursory checking, but given the kinds of changes this PR makes, App, PD, and LL should really go through each of their full QA suites before the next release with this change.
The best testing you can do is just stress testing. Be on the lookout for: