Has anybody else noticed that the CDN access to fontawesome is broken? Fortunately I was able to install the npm package and put the following in my code
import '@fortawesome/fontawesome-free/js/all.js';
Has anybody else noticed that the CDN access to fontawesome is broken? Fortunately I was able to install the npm package and put the following in my code
import '@fortawesome/fontawesome-free/js/all.js';
Yep noticed that last week, kept getting connection errors in the console. Seems to be intermittent though as it started working again.
And the CDN is down again. Does anybody have a better solution than using their CDN? I tried the npm package, but it converts all font awesome icons into svg image …
And it’s back. Still would be interested in an alternative to the CDN
They had the same issue last week, impacting couple of our projects.
Ok, the CDN is down again, switched to npm. Did the following in my project
$ meteor npm install --save @fortawesome/fontawesome-free
$ cd public && ln -s ../node_modules/@fortawesome/fontawesome-free/webfonts
and in my main file I included
import '@fortawesome/fontawesome-free/css/all.min.css';
Hmm, looks like Galaxy doesn’t like symbolic links. With the above link in public an app deployed to galaxy doesn’t display anything shipped in /public. Instead of a symbolic link I had to copy the webfonts directory from node_modules to public and it worked again