2020-02-06
3044
#gatsby
Yomi Eluwande
13623
Feb 6, 2020 ⋅ 10 min read

Build responsive components in Gatsby with artsy/fresnel

Yomi Eluwande JavaScript developer. Wannabe designer and Chief Procrastinator at Selar.co and worklogs.co.

Recent posts:

ai dev tool power rankings

AI dev tool power rankings & comparison [Feb. 2026]

Compare the top AI development tools and models of February 2026. View updated rankings, feature breakdowns, and find the best fit for you.

Chizaram Ken
Feb 13, 2026 ⋅ 10 min read

How to solve package validation pain with Publint

Broken npm packages often fail due to small packaging mistakes. This guide shows how to use Publint to validate exports, entry points, and module formats before publishing.

Rahul Chhodde
Feb 12, 2026 ⋅ 5 min read
feb 11 the replay

The Replay (2/11/26): React performance wins, fine-grained frameworks, and more

Discover what’s new in The Replay, LogRocket’s newsletter for dev and engineering leaders, in the February 11th issue.

Matt MacCormack
Feb 11, 2026 ⋅ 34 sec read
react optimization shruti kapoor

A complete guide to React performance optimization

Cut React LCP from 28s to ~1s with a four-phase framework covering bundle analysis, React optimizations, SSR, and asset/image tuning.

Shruti Kapoor
Feb 11, 2026 ⋅ 9 min read
View all posts

3 Replies to "Build responsive components in Gatsby with artsy/fresnel"

  1. This article helped – I ran into issues with my Gatsby site and react-responsive. This package solved my issues, but now I’ve got a new one:

    I was utilizing a custom SEO component to modify page titles and meta tags. With this solution, I’m no longer seeing updated titles for each of my pages. I imagine it has something to do with the overridden html.js. Any ideas?

  2. Please correct the gatsby-ssr.js/gatsby-browser.js changes.
    It should be:

    export const wrapRootElement = ({ element }) => (
    {element}
    )

  3. I had to destructure element to get this to work ie: return { …element }

    Not sure if this is correct, but it worked for me.

Leave a Reply

Hey there, want to help make our blog better?

Join LogRocket’s Content Advisory Board. You’ll help inform the type of content we create and get access to exclusive meetups, social accreditation, and swag.

Sign up now