Hi @AquaL1te and @e3hines,
I made an update to the component that fixes the bug you both ran into.
The issue was that the component code was previously matching the wrong tag for a specific icon. In AquaL1te’s site this is quite obvious:
When the component was looking for an icon for jitsi it was wrongly matching it to get the icon (and then in a second step only, it was checking the full tag name, and since there was no match, it was showing nothing).
If you update the component, you should see the issue fixed.
Because Font Awesome has multiple sets of icons, the brand icons need a prefix. Try using fab-google, that should work. (And sorry it took me so long to respond to this…)