Replace material-icons with @material-design-icons/font#468
Merged
Conversation
chrismayer
approved these changes
Dec 16, 2025
Collaborator
chrismayer
left a comment
chrismayer
left a comment
There was a problem hiding this comment.
Thanks for this @sronveaux.
I am fine with the replacement. I did a quick visual check and everything seems to be OK in the UI.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 simple PR is part of the updates linked to #324.
I propose here to replace material-icons with @material-design-icons/font which, as stated in official Google repository is the same icon font but lighter as only the
woff2format is included. This removes an overhead of a bit more than 1MB in the build.Comparison of the included
woff2binary files in both packages was done and they are identical as expected.Dropping the
woffformat completely makes sense aswoff2is now correctly used by all mainstream browsers since 2016. Only in case of legacy browsers compatibility would this be needed which was dropped when transiting toVite.A note about this could be added, if you think it is useful, when proposing the
Viteplugin (which removes all formats of@mdiexceptwoff2) in an upcoming PR...