-
Notifications
You must be signed in to change notification settings - Fork 659
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
Warning: Using UNSAFE_componentWillMount in strict mode is not recommended and may indicate bugs in your code. #623
Comments
Duplicate, original issue here: #548 |
There is no solution other than |
|
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? |
What in the world? |
Is this library maintained anymore? Last publish was 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?
The text was updated successfully, but these errors were encountered: