Use a better default browser list and fail gracefully when css parsing fails #3509
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.
This PR has three different fixes:
Asset minification for CSS that lightning css doesn't parse. If lightning css fails, we log the error and fall back to the unminified css.
Lightning css defaults to supporting only the newest browsers which was causing CSS minifier is cutting out some css attributes #3289. Instead this PR switches to the browserslist defaults (or the browserlist file in your project)
It also fixes assets not being processed after hot reloading which can cause visual inconsistencies and makes debugging asset optimization difficult
Fixes #3372
Fixes #3289
Fixes #3471
Fixes #3310