Warning: Using UNSAFE_componentWillMount in strict mode is not recommended and may indicate bugs in your code.

nfl / react-helmet

A document head manager for React

MIT License

17.28k stars 657 forks source link

Warning: Using UNSAFE_componentWillMount in strict mode is not recommended and may indicate bugs in your code. #623

Open pxim opened 3 years ago

pxim commented 3 years ago

Do you want to request a feature or report a bug?

What is the current behavior?

Which versions of React and react-helmet, and which browser / OS are affected by this issue? Did this work in previous versions of React and/or react-helmet?

 "react": "^16.11.0",
 "react-dom": "^16.11.0",
 "react-helmet": "^6.1.0",

DevShahidul commented 3 years ago

Please check this solution https://stackoverflow.com/questions/62202890/how-can-i-fix-using-unsafe-componentwillmount-in-strict-mode-is-not-recommended

Maxou44 commented 3 years ago

Duplicate, original issue here: https://github.com/nfl/react-helmet/issues/548

pxim commented 3 years ago

There is no solution other than react helmet async.

hc0503 commented 1 year ago

There is no solution other than react helmet async.

react-helmet-async package works well.

t-ricci-digit commented 1 year ago

I don't get why the issue in this repository (react-helmet) should be avoided by ditching this (react-helmet) entirely and switch to another library (react-helmet-async with different owner of the repo)

Can't the issue be fixed in this repository with an update? Should we all just stop using react-helmet? I mean if another package made it work (react-helmet-async), why can't also this (react-helmet) change to React's standard recommendations?

kevr commented 1 year ago

What in the world?

ARogueOtaku commented 1 year ago

Is this library maintained anymore? Last publish was 3 years ago. I think the least the maintainer/former maintainer could do is update the README and redirect the new users to a suitable alternative.