Closed Fr0stM0urne closed 4 months ago
Ah, that's interesting, hmm.
There are some substantial font changes coming here soon which will resolve this anyway, so for now I think it's not worth properly this, sorry! The dependency on that service will go away completely within the next couple of weeks for a totally different approach, so I'll close this issue.
In the meantime though, if this is causing problems for you then you can probably work around this most easily by just disabling that webpack plugin entirely (commenting out this block). You'll end up with slightly wrong fonts, but that's probably fine for the short term. If you really want the 'right' fonts on your local setup, you could download and install them locally, and then everything will work without any 3rd party fonts required at all.
Running ui locally using
npm run start:web
. Constantly failing to fetch font urls such ashttps://gwfh.mranftl.com/api/fonts
,https://gwfh.mranftl.com/api/fonts/lato?subsets=latin
.This results in Uncaught Exceptions.
Possibly network issues on my end. However, is it worthwhile/possible to have the fonts downloaded locally and local content is accessed if there is a failure in URL fetch?