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
Warning: Using UNSAFE_componentWillMount in strict mode is not recommended and may indicate bugs in your code
Describe the bug
I get the following warning in the console -
client.js:1 Warning: Using UNSAFE_componentWillMount in strict mode is not recommended and may indicate bugs in your code. See https://reactjs.org/link/unsafe-component-lifecycles for details.
* Move code with side effects to componentDidMount, and set initial state in the constructor.
Please update the following components: SideEffect(NullComponent)
It is caused by react-helmet which is outdated now and started throwing error in the console.
Is this a regression?
Steps To Reproduce the error
simply running npm run dev after hooking up your WP url.
Expected behaviour
No warning of such.
CodeSandbox or Live Example of Bug
Screenshot or Video Recording
Your environment
OS: OS Name: Microsoft Windows 11 Home Single Language
OS Version: 10.0.22621 N/A Build 22621
Node version: v19.7.0
Npm version: 9.6.5
Browser name and version: Ms Edge Version 116.0.1938.69
Additional context
The text was updated successfully, but these errors were encountered:
NafiurSiddiqui
changed the title
[Bug]
[Bug] Warning: Using UNSAFE_componentWillMount in strict mode...
Sep 2, 2023
Bug Report
Warning: Using UNSAFE_componentWillMount in strict mode is not recommended and may indicate bugs in your code
Describe the bug
I get the following warning in the console -
It is caused by
react-helmet
which is outdated now and started throwing error in the console.Is this a regression?
Steps To Reproduce the error
npm run dev
after hooking up your WP url.Expected behaviour
No warning of such.
CodeSandbox or Live Example of Bug
Screenshot or Video Recording
Your environment
OS Version: 10.0.22621 N/A Build 22621
Additional context
The text was updated successfully, but these errors were encountered: