Font loader optimized for maximum performance. Removes render-blocking font resources and loads them asynchronusly. Handle FOUT & FOUC with font loading status watcher. Supports both local-hosted fonts and web fonts.
My Gatsby project is using npm-typefaces to self-host fonts, so the font files live in the node_modules folder.
For self-hosted fonts, the plugin requires a statically-typed path to the css file (i.e. the "file" param) where the @font-face lives.
In this case, using npm-typefaces, the filename of the css where the @font-face lives is determined at build time (e.g. /public/styles.46589de85f365befd1a4.css) and the fonts live in the public/static/ folder.
Is there a way to use this plugin with npm-typeface?
My Gatsby project is using npm-typefaces to self-host fonts, so the font files live in the node_modules folder.
For self-hosted fonts, the plugin requires a statically-typed path to the css file (i.e. the "file" param) where the @font-face lives.
In this case, using npm-typefaces, the filename of the css where the @font-face lives is determined at build time (e.g. /public/styles.46589de85f365befd1a4.css) and the fonts live in the public/static/ folder.
Is there a way to use this plugin with npm-typeface?