gatsby-ssr.js

/**
 * Creates a preload link pointing to myFonts' licence counting url. This
 * allows hits to the site to register as font requests with myFonts, but
 * ensures that we are not blocking CSS rendering by waiting for this request
 * to complete.
 *
 * This avoids having to include the following in a CSS file:
 * @import url("//hello.myfonts.net/count/<id>");
 *
 * Refs:
 * https://stackoverflow.com/questions/23045705/how-the-licensed-web-font-is-getting-rendered
 * https://developer.mozilla.org/en-US/docs/Web/HTML/Preloading_content
 */

const React = require("react");

exports.onRenderBody = function({ setHeadComponents }, pluginOptions) {
  setHeadComponents([
    React.createElement("link", {
      key: "fonts",
      href: `//hello.myfonts.net/count/${pluginOptions.myFontsId}`,
      rel: "preload",
      as: "style"
    })
  ]);
};

I know this is not a help forum, but I struggled with the pluginOptions.myFontsId implementation. I've read in docs that I can set it up in gatsby-config.js but wasn't able to figure it out - hardcoded it for my use-case. Was wondering how'd you go about setting it up in gatsby-config if you're willing to share :)

I don't actually remember how I did this 😬 and I don't have access to the code that I wrote this for any more. Doing a bit of digging, I'm guessing that this gatsby-ssr.js file was part of a local plugin.

You could then pass the config options in as part of the plugin config. I found an example site with that approach: https://github.com/gatsbyjs/gatsby/tree/master/examples/using-plugin-options. And there's a bit more info on local plugins here: https://github.com/gatsbyjs/gatsby-starter-plugin.

tbh hardcoding the id seems like a nice and simple way to do it. I hope that helps!

Thank you! 👍