This package is deprecated. There are now easier ways to embed Typekit fonts into your apps with a simple CSS include. This package uses the JS Embed Code method, but it provides no benefit over including the script yourself, and only causes issues if used incorrectly. Please read the embed fonts page for more information.
This React component will generate the Adobe Typekit script required to load your webfont bundles. Though it can be used anywhere, this works great for isomorphic/universal React applications that render the entire DOM structure in React components.
w/ NPM
npm install --save react-typekitw/ Yarn
yarn add react-typekitPass your Typekit Kit ID as a prop to the Typekit component. You can find this ID by logging into Adobe Typekit.
import React from 'react';
import Typekit from 'react-typekit';
const HtmlLayout = () => (
<html>
<body>
<h1>My Example React Component</h1>
<Typekit kitId="abc123" />
</body>
</html>
);
export default HtmlLayout;If you are loading fonts from Adobe Typekit on your website, and checked your website with DevTools in Chrome after December 1st 2017, you might have seen these notices:
The SSL certificate used to load resources from https://use.typekit.net will be distrusted in M70. Once distrusted, users will be prevented from loading these resources. See https://g.co/chrome/symantecpkicerts for more information.
The SSL certificate used to load resources from https://p.typekit.net will be distrusted in M70. Once distrusted, users will be prevented from loading these resources. See https://g.co/chrome/symantecpkicerts for more information.
The notices are not caused by your website’s SSL certificate, but because Adobe Typekit service uses SSL certificates issued by Symantec’s infrastructure, certificates that were found to be not up to industry standards. The link in the notice is very helpful, it’s a detailed article written on the official Google Security Blog where the notices are thoroughly explained. I recommend you read it.
You don’t need to make any change to your website, or push the panic button. It’s something Adobe has to fix before the release of version 70 of Google Chrome on October 23, 2018. Your font service is not affected in any way until then. For any questions about this I would recommend to contact the Adobe’s support team, it’s not something theme related.
