<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Adam J. Arling on Medium]]></title>
        <description><![CDATA[Stories by Adam J. Arling on Medium]]></description>
        <link>https://medium.com/@adamjarling?source=rss-120196a7dd1c------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*AlT6eqkwTDw36UbHIOp8HA.jpeg</url>
            <title>Stories by Adam J. Arling on Medium</title>
            <link>https://medium.com/@adamjarling?source=rss-120196a7dd1c------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Wed, 18 Nov 2026 01:06:57 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@adamjarling/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Dive into Environment Variables in Next.js: Security, Flexibility, and CMS Integration]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@adamjarling/dive-into-environment-variables-in-next-js-security-flexibility-and-cms-integration-8f04b19447b1?source=rss-120196a7dd1c------2"><img src="https://cdn-images-1.medium.com/max/1024/1*w6atZNMuXTgUysw4XLlBHQ.jpeg" width="1024"></a></p><p class="medium-feed-snippet">Unleash flexibility and security for your builds with Next.js&#x2019;s environment variable system.</p><p class="medium-feed-link"><a href="https://medium.com/@adamjarling/dive-into-environment-variables-in-next-js-security-flexibility-and-cms-integration-8f04b19447b1?source=rss-120196a7dd1c------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@adamjarling/dive-into-environment-variables-in-next-js-security-flexibility-and-cms-integration-8f04b19447b1?source=rss-120196a7dd1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/8f04b19447b1</guid>
            <category><![CDATA[github-actions]]></category>
            <category><![CDATA[nextjs]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[environmental-variables]]></category>
            <category><![CDATA[javascript]]></category>
            <dc:creator><![CDATA[Adam J. Arling]]></dc:creator>
            <pubDate>Sun, 04 Feb 2024 17:51:17 GMT</pubDate>
            <atom:updated>2024-02-04T17:51:17.506Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Getting started with GitHub Copilot for Front End Developers]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@adamjarling/getting-started-with-github-copilot-for-front-end-developers-8c06806b2756?source=rss-120196a7dd1c------2"><img src="https://cdn-images-1.medium.com/max/1024/1*VW5z5rDyB1oE9aNmWMxocw.png" width="1024"></a></p><p class="medium-feed-link"><a href="https://medium.com/@adamjarling/getting-started-with-github-copilot-for-front-end-developers-8c06806b2756?source=rss-120196a7dd1c------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@adamjarling/getting-started-with-github-copilot-for-front-end-developers-8c06806b2756?source=rss-120196a7dd1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/8c06806b2756</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[generative-ai-tools]]></category>
            <category><![CDATA[github-copilot]]></category>
            <category><![CDATA[front-end-development]]></category>
            <dc:creator><![CDATA[Adam J. Arling]]></dc:creator>
            <pubDate>Fri, 07 Jul 2023 20:23:26 GMT</pubDate>
            <atom:updated>2023-07-08T12:21:23.020Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Get Organized: How to Auto Sort Your JavaScript Imports with ESLint]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://javascript.plainenglish.io/get-organized-how-to-auto-sort-your-javascript-imports-in-vscode-34d786972112?source=rss-120196a7dd1c------2"><img src="https://cdn-images-1.medium.com/max/1920/1*-ZIyLRPu3BGrwir4EqKYQg.jpeg" width="1920"></a></p><p class="medium-feed-snippet">When working on large projects with multiple contributors, it can be challenging to maintain a consistent coding style. This is important&#x2026;</p><p class="medium-feed-link"><a href="https://javascript.plainenglish.io/get-organized-how-to-auto-sort-your-javascript-imports-in-vscode-34d786972112?source=rss-120196a7dd1c------2">Continue reading on JavaScript in Plain English »</a></p></div>]]></description>
            <link>https://javascript.plainenglish.io/get-organized-how-to-auto-sort-your-javascript-imports-in-vscode-34d786972112?source=rss-120196a7dd1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/34d786972112</guid>
            <category><![CDATA[vscode]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[eslint]]></category>
            <category><![CDATA[code-quality]]></category>
            <dc:creator><![CDATA[Adam J. Arling]]></dc:creator>
            <pubDate>Tue, 28 Feb 2023 15:46:14 GMT</pubDate>
            <atom:updated>2024-07-24T01:09:39.190Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Create flexible functions using TypeScript generics]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@adamjarling/how-to-use-generics-in-typescript-functions-c6f69c9af5ee?source=rss-120196a7dd1c------2"><img src="https://cdn-images-1.medium.com/max/2600/1*vcNKjHivrf7fiobBRgl0EA.jpeg" width="3024"></a></p><p class="medium-feed-snippet">TypeScript is a powerful programming language that adds optional static typing and other advanced features to JavaScript. A key feature is&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@adamjarling/how-to-use-generics-in-typescript-functions-c6f69c9af5ee?source=rss-120196a7dd1c------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@adamjarling/how-to-use-generics-in-typescript-functions-c6f69c9af5ee?source=rss-120196a7dd1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/c6f69c9af5ee</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[react]]></category>
            <dc:creator><![CDATA[Adam J. Arling]]></dc:creator>
            <pubDate>Fri, 24 Feb 2023 17:02:30 GMT</pubDate>
            <atom:updated>2023-03-01T18:01:21.001Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Catch TypeScript Errors in Next.js Before Building Your App]]></title>
            <link>https://javascript.plainenglish.io/catch-typescript-errors-in-nextjs-before-building-your-app-df129682ee5c?source=rss-120196a7dd1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/df129682ee5c</guid>
            <category><![CDATA[programming]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[nextjs]]></category>
            <category><![CDATA[typescript]]></category>
            <dc:creator><![CDATA[Adam J. Arling]]></dc:creator>
            <pubDate>Fri, 11 Mar 2022 23:25:39 GMT</pubDate>
            <atom:updated>2023-03-13T05:35:08.063Z</atom:updated>
            <content:encoded><![CDATA[<h4>Automate the task to catch type errors in Next.js</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Uaa_I0UW0uaWFQ_nVG2OYQ.jpeg" /></figure><p>Recently our dev team at <a href="https://github.com/nulib">Northwestern Libraries</a> has been transitioning to <a href="https://www.typescriptlang.org/">TypeScript</a> in our <a href="https://nextjs.org/">Next.js</a> UI applications. We’ve come across a “gotcha” twice now with CI build failures when the dev environment seemingly ran fine. It’s a simple solution, but perhaps one which might save you a bit of time and head-scratching.</p><h3>The issue</h3><p>An application codebase runs successfully in local dev mode, but when pushed to the app’s CI (<a href="https://en.wikipedia.org/wiki/Continuous_integration">Continuous Integration</a>) pipeline, building on staging fails.</p><p>Hmmm. We ran Next.js’s pre-wired next lint script like a responsible developer and everything checked out fine. We try Next.js’s next build script, and there it is; build failure.</p><h3><strong>A manual solution</strong></h3><p>One solution is to remember to manually run next build before every git commit, because next build seems to catch TypeScript type errors under the hood, somehow. Chances of (at least myself) remembering to manually run this every time? Not good.</p><h3>Or…an automated solution</h3><p>How could automate this task in Next.js to catch type errors before pushing up code for pull requests, and just not even think about it?</p><p>One option is setting up <em>a </em><a href="https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks#:~:text=The%20pre%2Dcommit%20hook%20is,to%20inspect%20in%20the%20code."><em>pre-commit hook</em></a><em>.</em></p><p>A pre-commit hook will run on git commit, before the actual commit happens.</p><p>A common use case is to run tests (unit or integration), as pre-commit hook actions to automate insurance of test coverage. What we want, however, is to add <em>type checking</em> to our code before a git commit happens.</p><p>As mentioned, the default Next.js configuration comes out of the box pre-wired with a next lint command. This command will catch JavaScript errors according to your <a href="https://eslint.org/">ESLint configuration</a>, but the ESLint configuration is not automatically aware of TypeScript, even when bootstrapping your Next.js app w/ TypeScript.</p><h3>The code</h3><p>Let’s add some code to help out. This is assuming your Next.js app is configured to use TypeScript. If so, you’ll have access to the TypeScript <a href="https://www.typescriptlang.org/docs/handbook/compiler-options.html">command line compiler tool</a>, tsc.</p><p>Add the following line to your package.json file’s scripts block:</p><pre>”ts-lint”: “tsc — noEmit — incremental — watch”,</pre><p>ts-lint could be called anything, FYI.</p><p>This command says, <em>“Type check the code, but don’t create type definitions in files or anything. Also keep watching the code and keep type checking as I’m developing”</em>.</p><p>package.json scripts block now should look something like this:</p><pre>&quot;scripts&quot;: {<br>  &quot;build&quot;: &quot;next build&quot;,<br>  &quot;dev&quot;: &quot;next dev&quot;,<br>  &quot;lint&quot;: &quot;next lint&quot;,<br>  ...<br>  &quot;ts-lint&quot;: &quot;tsc --noEmit --incremental --watch&quot;,<br>  ...<br>},</pre><p>Try manually running ts-lint in your Terminal. Any type errors? Fix ’em up!</p><h3>Add the pre-commit hook</h3><p>Now let&#39;s wire up a pre-commit hook.</p><p>Step one, install the husky <a href="https://www.npmjs.com/package/husky">NPM package</a> as a dev dependency to your app.</p><pre>npm install -D husky</pre><pre>// or via yarn<br>yarn add -D husky</pre><p><a href="https://typicode.github.io/husky/">Husky</a> is a lightweight helper to tie into commit workflow.</p><p>Let’s do a quick configuration of husky once installed. For more details or manual configuration, <a href="https://typicode.github.io/husky/#/?id=automatic-recommended">check out the docs</a>. Oh, and before running the following commands, make sure your package.json file is saved.</p><p>Depending on whether you use npm or yarn, here’s a snippet from husky’s docs on how to run the automated configuration:</p><pre># NPM<br>npx husky-init &amp;&amp; npm install</pre><pre># Yarn 1<br>npx husky-init &amp;&amp; yarn</pre><pre># Yarn 2<br>yarn dlx husky-init --yarn2 &amp;&amp; yarn</pre><p>Running this husky-init config script does a few things:</p><ol><li>Modifies your package.json file to add husky to your scripts block, which allows its execution.</li><li>Creates a .husky directory in the root of your project with the pre-commit hook you want to run. And also which you can (and we will) edit.</li></ol><p>By default, the automated husky configuration creates the command npm run test. For this article’s example, let’s change npm run test to something that runs type checking on our code.</p><h3>Add a pre-commit command</h3><p>Now add the following new command to our package.json file scripts block. It looks quite similar to the previous ts-lint command above, except this command doesn’t watch our code. One and done.</p><pre>&quot;ts-lint-commit-hook&quot;: &quot;tsc --noEmit --incremental&quot;,</pre><p>Now open the .husky/pre-commit file in your project and let’s update husky ‘s pre-commit command:</p><pre>#!<em>/bin/sh<br></em>. &quot;$(dirname &quot;$0&quot;)/_/husky.sh&quot;</pre><pre>// OLD<br><em># npm run test</em></pre><pre><em>// NEW<br>npm run ts-lint-commit-hook</em></pre><p>And that’s it. Now with every commit, your TypeScript code will get type-checked ensuring it contains no type errors before your code enters any CI workflows. If it’s going to fail, you’re going to know it before your teammates do. 😁</p><p>Check out a <a href="https://github.com/nulib/dc-nextjs">working implementation</a> in a new Digital Collections application we’re building for our Northwestern Libraries repository using Next.js, <a href="https://www.radix-ui.com/">Radix</a>, <a href="https://stitches.dev/">Stitches</a>, and a <a href="https://github.com/nulib/design-system">new design system</a> we’re building.</p><p><a href="https://github.com/nulib/dc-nextjs">GitHub - nulib/dc-nextjs: Playground for NextJS Digital Collections</a></p><h3>Next.js is powerful</h3><p><a href="https://nextjs.org/">Next.js</a> is a powerful, next-generation platform for building React-based projects. Combined with bug reduction via type checking in TypeScript, you can build anything from static Single Page Apps, component libraries, a Node API, to hybrid server-side rendered apps thousands if not millions of pages large.</p><p><em>More content at </em><a href="https://plainenglish.io/"><strong><em>PlainEnglish.io</em></strong></a><em>. Sign up for our </em><a href="http://newsletter.plainenglish.io/"><strong><em>free weekly newsletter</em></strong></a><em>. Follow us on </em><a href="https://twitter.com/inPlainEngHQ"><strong><em>Twitter</em></strong></a><em> and </em><a href="https://www.linkedin.com/company/inplainenglish/"><strong><em>LinkedIn</em></strong></a><em>. Join our </em><a href="https://discord.gg/GtDtUAvyhW"><strong><em>community Discord</em></strong></a><em>.</em></p><h4>Further Reading</h4><p><a href="https://javascript.plainenglish.io/typescript-made-easy-a-guide-to-your-first-type-safe-app-with-next-js-wundergraph-and-prisma-e197a59e2b30">TypeScript Made Easy: A Guide To Your First Type-Safe App with Next.js, WunderGraph, and Prisma</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=df129682ee5c" width="1" height="1" alt=""><hr><p><a href="https://javascript.plainenglish.io/catch-typescript-errors-in-nextjs-before-building-your-app-df129682ee5c">Catch TypeScript Errors in Next.js Before Building Your App</a> was originally published in <a href="https://javascript.plainenglish.io/">JavaScript in Plain English</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Build and Package an NPM Component with esbuild, React and TypeScript]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://javascript.plainenglish.io/develop-and-publish-a-react-component-with-esbuild-and-typescript-3eb756adda6e?source=rss-120196a7dd1c------2"><img src="https://cdn-images-1.medium.com/max/885/1*XYEs0ooJcS68pDPIseKXUA.png" width="885"></a></p><p class="medium-feed-snippet">Looking for a simple, straightforward, development environment for a React component(s) that can be bundled and packaged for NPM&#x2026;</p><p class="medium-feed-link"><a href="https://javascript.plainenglish.io/develop-and-publish-a-react-component-with-esbuild-and-typescript-3eb756adda6e?source=rss-120196a7dd1c------2">Continue reading on JavaScript in Plain English »</a></p></div>]]></description>
            <link>https://javascript.plainenglish.io/develop-and-publish-a-react-component-with-esbuild-and-typescript-3eb756adda6e?source=rss-120196a7dd1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/3eb756adda6e</guid>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[typescript]]></category>
            <category><![CDATA[programming]]></category>
            <dc:creator><![CDATA[Adam J. Arling]]></dc:creator>
            <pubDate>Mon, 03 Jan 2022 22:17:56 GMT</pubDate>
            <atom:updated>2022-01-06T14:34:12.318Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Using React Hook Form in component tests]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://javascript.plainenglish.io/using-react-hook-form-in-component-tests-497180abf3c0?source=rss-120196a7dd1c------2"><img src="https://cdn-images-1.medium.com/max/1469/1*qNxKt-9OmzfjFsPv6LfEKQ.png" width="1469"></a></p><p class="medium-feed-snippet">React Hook Form is an incredibly useful package for building out simple to complex web forms. This article illustrates our team&#x2019;s approach&#x2026;</p><p class="medium-feed-link"><a href="https://javascript.plainenglish.io/using-react-hook-form-in-component-tests-497180abf3c0?source=rss-120196a7dd1c------2">Continue reading on JavaScript in Plain English »</a></p></div>]]></description>
            <link>https://javascript.plainenglish.io/using-react-hook-form-in-component-tests-497180abf3c0?source=rss-120196a7dd1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/497180abf3c0</guid>
            <category><![CDATA[react]]></category>
            <category><![CDATA[testing-library]]></category>
            <category><![CDATA[react-hook-form]]></category>
            <category><![CDATA[javascript]]></category>
            <category><![CDATA[react-testing-library]]></category>
            <dc:creator><![CDATA[Adam J. Arling]]></dc:creator>
            <pubDate>Sun, 27 Sep 2020 19:46:49 GMT</pubDate>
            <atom:updated>2021-02-11T20:40:51.814Z</atom:updated>
        </item>
        <item>
            <title><![CDATA[Share Website Preview Images in Gatsby]]></title>
            <link>https://medium.com/swlh/share-website-preview-images-in-gatsby-10cac58dd4d7?source=rss-120196a7dd1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/10cac58dd4d7</guid>
            <category><![CDATA[gatsbyjs]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[open-graph]]></category>
            <category><![CDATA[gatsby]]></category>
            <category><![CDATA[static-site-generator]]></category>
            <dc:creator><![CDATA[Adam J. Arling]]></dc:creator>
            <pubDate>Thu, 27 Aug 2020 20:35:47 GMT</pubDate>
            <atom:updated>2020-09-04T06:44:57.678Z</atom:updated>
            <content:encoded><![CDATA[<h3>Share Website Preview Images in Gatsby With the Open Graph Protocol</h3><p>When sharing web content across phone, tablet, or laptop, image previews of a website provide a valuable first impression. If you’re developing websites using static site generators in the <a href="https://reactjs.org/">React</a> ecosystem, such as <a href="https://www.gatsbyjs.com/">Gatsby</a> or <a href="https://nextjs.org/">Next.js</a>, it’s not immediately clear (or at least wasn’t to me) on how to integrate and customize preview images.</p><p>This article will show how to create preview images using the <a href="https://ogp.me/">Open Graph protocol</a>.</p><p>Maybe you’ve pasted a URL to share with a friend and it looks like this:</p><figure><img alt="Open Graph image unsuccessful preview" src="https://cdn-images-1.medium.com/max/750/1*NJjkxHR5me0aXbmWFY9abA.jpeg" /></figure><p>Let’s get that preview image more exciting.</p><h3>Standard HTML Open Graph implementation</h3><p>Using the <a href="https://ogp.me/">Open Graph</a> protocol, websites can display preview content of your choosing, including image, title, description and more.</p><p>If you’re building an HTML website from scratch and have access to the entire HTML files directly, implementing preview content using Open Graph is pretty straightforward by adding &lt;meta /&gt; HTML elements.</p><pre>&lt;html prefix=&quot;og: https://www.furbaby.rocks&quot;&gt;<br>&lt;head&gt;<br>&lt;title&gt;Furbaby Rocks&lt;/title&gt;<br>&lt;meta property=&quot;og:title&quot; content=&quot;Furbaby is a garage rock band&quot; /&gt;<br>&lt;meta property=&quot;og:image&quot; content=&quot;https://www.furbaby.rocks/images/og-image.jpg&quot; /&gt;<br>...<br>&lt;/head&gt;<br>...<br>&lt;/html&gt;</pre><p>There’s additional Open Graph metadata options including <em>audio, description, locale, video</em> and more, to further describe content. <a href="https://ogp.me/#optional">View optional Open Graph metadata properties</a>.</p><h3>Gatsby Open Graph implementation</h3><p>When using a JavaScript static site generator package (such as <a href="https://www.gatsbyjs.com/">Gatsby</a>, which we’ll use as an example), you can’t really update the &lt;head /&gt; markup of a Gatsby site’s HTML files directly. Static site generators build and compile HTML files for you, and it’s common to have the &lt;head /&gt; section abstracted away from component development.</p><p>So, basically we want to say:</p><blockquote>“Hey Gatsby, when you’re building my React components into static HTML files, include some Open Graph &lt;meta /&gt; tags, including a tag which shows a cool preview image when I’m sharing my website url.”</blockquote><p>Take Chicago garage-rock band <a href="https://www.furbaby.rocks/">Furbaby’s Gatsby site</a> as a code example. <a href="https://github.com/adamjarling/furbaby">https://github.com/adamjarling/furbaby</a></p><p>There’s a re-usable &lt;SEO /&gt; component which each Gatsby page component imports to add unique search engine optimization data on a page by page basis.</p><iframe src="" width="0" height="0" frameborder="0" scrolling="no"><a href="https://medium.com/media/86c3d826625ca9dcf90745670b6873a6/href">https://medium.com/media/86c3d826625ca9dcf90745670b6873a6/href</a></iframe><blockquote>What is <a href="https://www.npmjs.com/package/helmet">Helmet</a>? We’re using the popular Helmet package to reach outside of our React component and “inject” code into the &lt;head /&gt; section of generated HTML.</blockquote><p>The key lines of code from the above gist are:</p><ul><li>Line #6: Import the preview image you’d like to use. <a href="https://developers.facebook.com/docs/sharing/webmasters/images/">Recommended image size</a> is 1200px x 630px, but you could make it square or experiment to taste.</li><li>Lines #22–25: This defines the Open Graph <em>image</em> property, and points to the local image file Open Graph will use when displaying a preview image. When you import an image in React, at build time Gatsby will render the proper path where the image ends up.</li></ul><h3>Verify Preview Image</h3><p>Ok, let’s see if our code additions worked.</p><p>In your local development environment, go back into your local terminal window and make a fresh build:</p><pre>// We&#39;re using Gatsby in this example</pre><pre>gatsby build</pre><p>Push up your fresh build to your server. Then send a friend a new message with the site URL link, and it should have your custom image content.</p><figure><img alt="Open Graph image successful preview" src="https://cdn-images-1.medium.com/max/750/1*YvvFFeVRAdeSGzncLEOVRA.jpeg" /></figure><h3>Verify using Facebook Debug Tools</h3><p>Facebook offers a convenient way to both view your existing Open Graph presence for a website, and also to test Open Graph property changes (so you don’t have to constantly bug friends with repeated test link sharing).</p><p><a href="https://developers.facebook.com/tools/debug/">https://developers.facebook.com/tools/debug/</a></p><h3>Conclusion</h3><p>This is just a simple example. Experiment with the <a href="https://ogp.me/">Open Graph</a> protocol to sample the possibilities of creating intrigue about your website’s often-timed first impression. Go rock out to <a href="https://www.furbaby.rocks/">Furbaby</a> already.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=10cac58dd4d7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/swlh/share-website-preview-images-in-gatsby-10cac58dd4d7">Share Website Preview Images in Gatsby</a> was originally published in <a href="https://medium.com/swlh">The Startup</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mocking a React Router match object in your component tests]]></title>
            <description><![CDATA[<div class="medium-feed-item"><p class="medium-feed-image"><a href="https://medium.com/@adamjarling/mocking-a-react-router-match-object-in-your-component-tests-fa95904dcc55?source=rss-120196a7dd1c------2"><img src="https://cdn-images-1.medium.com/max/1044/1*_hmhjPbBJ_CPTNb_EE8w8w.png" width="1044"></a></p><p class="medium-feed-snippet">Recently our UI team has switched from Enzyme to Kent Dodd&#x2019;s Testing Library for a much improved, simplified experience in testing&#x2026;</p><p class="medium-feed-link"><a href="https://medium.com/@adamjarling/mocking-a-react-router-match-object-in-your-component-tests-fa95904dcc55?source=rss-120196a7dd1c------2">Continue reading on Medium »</a></p></div>]]></description>
            <link>https://medium.com/@adamjarling/mocking-a-react-router-match-object-in-your-component-tests-fa95904dcc55?source=rss-120196a7dd1c------2</link>
            <guid isPermaLink="false">https://medium.com/p/fa95904dcc55</guid>
            <category><![CDATA[unit-testing]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[react-testing-library]]></category>
            <category><![CDATA[jest]]></category>
            <dc:creator><![CDATA[Adam J. Arling]]></dc:creator>
            <pubDate>Tue, 24 Sep 2019 21:21:07 GMT</pubDate>
            <atom:updated>2019-09-25T03:23:28.757Z</atom:updated>
        </item>
    </channel>
</rss>