Skip to content
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

Swap out react helmet #259

Merged
merged 10 commits into from
Jan 13, 2022
Merged

Swap out react helmet #259

merged 10 commits into from
Jan 13, 2022

Conversation

NickCallaghan
Copy link
Member

So it turns out the UNSAFE__componentWillMount warning we see in the console was actually being caused by react-helmet. There's details of the issue [here(https://github.com/nfl/react-helmet/issues/548)

As a fix i've swapped it out for react-helmet-async.

@netlify
Copy link

netlify bot commented Dec 23, 2021

❌ Deploy Preview for climatemind-storybook failed.

🔨 Explore the source changes: cec2493

🔍 Inspect the deploy log: https://app.netlify.com/sites/climatemind-storybook/deploys/61dfe25d7362ae00079b1460

@NickCallaghan NickCallaghan merged commit b0d2622 into develop Jan 13, 2022
@NickCallaghan NickCallaghan deleted the swap_out_react_helmet branch January 16, 2022 09:46
@onpaws
Copy link

onpaws commented Jan 24, 2022

Having also experienced the issue of react-helmet and these console warnings, I was also considering react-helmet-async, but then I noticed that Next apparently ships their own HeadManager

I was curious if there were reasons you went with react-helmet-async anyway?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants