Tags
I finally fixed my Styled-Components in gatsby.js. I am starting a redesign of
my website. I have started cross posting to dev.to more
regularly. With that I have been making more detailed cover images at the
recommended 1000x420. These images get cut off on my own site, which is a
bit ridiculous to have my own content not look right on my own site. But
before we start a heavy redesign I have a small issue that has plagued the site
for at least a year!
I have a small issue that has plagued the site for at least a year!
I have been using styled components in my gatsby.js site for about a year now. And it has been plagued by styled-components not being in the ssr causing some jank in the styles being loaded. You can see it in the lighthouse performance report below. It generally loads super quick, and is only caused on first load. Anything using the gatsby <Link/> component typically is fine and unaffected by the issue.
The fix
The fix was so simple it was only 2 lines total. One to install gatsby-plugin-styled-components and one to use it.
npm i gatsby-plugin-styled-components
plugins: [ 'gatsby-plugin-styled-components', ]
Before
After
Why did it take so long to Fix?
The real issue here was that I really didn't understand the problem as I described it above until I found the fix. It really did seem random that at odd times the styles would seem to vanish. Sometimes never fully rehydrating at all. Well actually I had fixed some production sites at work with it, but had no idea why it worked and therefore could not remember how I had fixed it, and google searched yielded no help.
After re-watching Wes Bos's Advanced react course where he describes how to fix this issue for next.js sites it became clear that the problem was not random at all. It was that they do not get statically rendered and are only on the page after react is re-hydrated. The moment I realized the true problem I knew how to google it and quickly found there was a plugin for this.