You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a neat new package called gatsby-plugin-next-seo with uses react-helmet-async instead of react-helmet. This plugin, however, requires you to use react-helmet. Is there a way to lift that requirement? I'd like to use any helmet lib.
Right now, when using both react-helmet's there are errors, like - for example - <title> is rendered empty.
I tried switching to react-helmet-async by overwriting gatsby-theme-material-ui-top-layout/components/viewport.js and replacing react-helmet with react-helmet-async but in the gatsby-node.js the gatsby-plugin-react-helmet is still required. I ultimately resolved this issue by using patch-package and removing those entries locally.
I could post a pull request with a change, but I'm unsure what's the best way to proceed.
Thanks
The text was updated successfully, but these errors were encountered:
jakubjafra
changed the title
Usage with gatsby-plugin-next-seo
Usage with gatsby-plugin-next-seo?
Jan 25, 2021
Hi! :)
There is a neat new package called gatsby-plugin-next-seo with uses
react-helmet-async
instead ofreact-helmet
. This plugin, however, requires you to usereact-helmet
. Is there a way to lift that requirement? I'd like to use any helmet lib.Right now, when using both
react-helmet
's there are errors, like - for example -<title>
is rendered empty.I tried switching to
react-helmet-async
by overwritinggatsby-theme-material-ui-top-layout/components/viewport.js
and replacingreact-helmet
withreact-helmet-async
but in thegatsby-node.js
thegatsby-plugin-react-helmet
is still required. I ultimately resolved this issue by using patch-package and removing those entries locally.I could post a pull request with a change, but I'm unsure what's the best way to proceed.
Thanks
The text was updated successfully, but these errors were encountered: