-
Notifications
You must be signed in to change notification settings - Fork 7
Feature Request: Remove usage of react-helmet
#32
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Hi Lennart. Thanks for the heads up. I've haven't been following Gatsby's development in the past few months, but I'm happy to improve the plugin if needed. I'm away on holiday for the next 10 days, hopefully I'll be able to pick this up once I'm back. I'll let you know if I run into any issues. |
Awesome, enjoy your vacation :) |
Hi @codeAdrian, I'm seeing if you have had any chance to look at this. I've been a super happy user of this plugin, and I'm migrating all of my code away from React Helmet and moving towards the native Gatsby head approach and I'm hoping to see this move in the more modern direction as well ;) Cheers! Thanks for a great product |
Same as @duffner here 👍 |
Hi, same here! |
Another +1 - using Gatsby v5 and would love to remove react-helmet 👍🏼 |
another plus 1 |
Hi!
With Gatsby 4.19 a Head API was released: https://www.gatsbyjs.com/docs/reference/release-notes/v4.19/#gatsby-head-api
I'm slowly removing
react-helmet
from all my projects and replace it with the Head API. To be able to completely remove thatreact-helmet
dependency this plugin would need to not rely onreact-helmet
.While you can't use Gatsby Head API for your plugin, you can use the normal
setHeadComponents
API. Or did you run into any problems when using that and opted for react-helmet? :)Happy to help with guidance on how to remove that peerDep.
Thanks!
The text was updated successfully, but these errors were encountered: