-
Notifications
You must be signed in to change notification settings - Fork 5.4k
chore: update sass to v1.71.0
#22531
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
f7f6bcb to
504a580
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #22531 +/- ##
========================================
Coverage 68.46% 68.46%
========================================
Files 1089 1089
Lines 43045 43045
Branches 11469 11469
========================================
Hits 29469 29469
Misses 13576 13576 ☔ View full report in Codecov by Sentry. |
Builds ready [504a580]
Page Load Metrics (536 ± 283 ms)
Bundle size diffs
|
|
👍 Dependency issues cleared. Learn more about Socket for GitHub ↗︎ This PR previously contained dependency changes with security issues that have been resolved, removed, or ignored. Ignoring: Next stepsTake a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with |
0d6fb1a to
4c0757e
Compare
Builds ready [7fed5b1]
Page Load Metrics (429 ± 196 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
5231e2a to
b3492e9
Compare
b3492e9 to
280886a
Compare
sass to v1.71.0
Builds ready [e70ef4b]
Page Load Metrics (441 ± 204 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
…tension into prepare-sass-update
Builds ready [2d9797e]
Page Load Metrics (1036 ± 406 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
|
@SocketSecurity ignore npm/sass-embedded@1.71.1 |
Updates Sass
Updates
sassto the latest version, while also switching tosass-embedded(maintained by the same team, is faster than sass, and we don't need to patch it anymore!).Moves fonts
This PR also moves the
fontsdirectory to be relative to the CSS file that imports it. This helps with two things:Use
@usefor the design-system instead of@importThe biggest change in this PR is moving towards the use of
@useand away from@import, which is slated to be completely removed from Sass in some distance future release.Bonus savings!
This PR also fixes a the duplication of CSS, as the design-system previously included actual CSS (colors, fonts, and font-awesome styles) and reduces the output size from ~1700KB to ~1300KB. The issue with that some devs were already
@useing thedesign-system, which was re-including its all of its rules (mentioned above).So, from now on, if someone wants to use something from the design-system they'll need to put
@use design-system";at the top of the SCSS file.