The Ents have decided…We have all agreed… that you two are not Orcs.
This all started with an issue on our private Font-Awesome-Pro GitHub repository. Our support for tree shaking was shaky at best, requiring an additional tool-specific configuration that was easy to miss.
We started down the path to fix the root issue related to tree shaking and ended up mixing in a little TypeScript, reconfiguring how we do packages, and changing how our underlying API is organized. This quickly became a breaking change. And Font Awesome 5.1 became necessary to signal the upgrade from 5.0.
I’m worried, Ray, it’s getting crowded in there and all my recent data points to something big on the horizon.
Our team has been hard at work on Font Awesome 5. At the time of this writing we are 96% complete converting the older version 4 icons. We’ve added completely new styles: Regular and Light. There are tons of new brand icons and new features such as the SVG Framework and Power Transforms.
We’ve received a lot of positive feedback but something caught my attention while I was reviewing the issues thread on our private Font-Awesome-Pro GitHub repository.
To make working with SVG a piece of
We recently had a Font Awesome CDN user ask us if there was a way to fallback to CSS-only when using an embed code.
If you haven’t heard of or tried our free CDN product you can register with us and get a brand new embed code of your own to play with by going to https://cdn.fontawesome.com.