Closed ChrisTav424 closed 2 years ago
Given problem might occur only if you have a fragmentation in React versions - it should be one react
and react-dom
Please check your lock file - that's the simplest way to find what you have.
The problem is happening on React level due to wrong initialisation or wrong singlentone used (more than one version) and is not related to this particular package. But this package might trigged pre-existing problem by accessing another version of React due to some random reason.
I have used the following on my page
But I am getting the following error. I assume I just have something wrong but can anyone help? Using React 17.0.2.