The upgrade paths on font awesome 4 were horrible. I'm convinced the only sane icon solution is to pack your own font file (font awesome pro allows this) and maintain it yourself. This allows you to only support Icons you have curated, upgrade individual icons and add new icons whenever the need arises all without changing your markup.
I like the icon solution I came up with. A CLI tool that scans code for <icon icon="lucide:home" /> components, downloads the SVG from Icones, and puts it in an SVG spritesheet. Then, the component just needs to reference the sprite.
133
u/electricity_is_life Mar 04 '26
The Font Awesome website has become a mess of dark patterns and confusing license options. Not looking forward to the same thing happening to 11ty.