Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Legacy context API has been detected within strict-mode tree
See original GitHub issueIs anyone having the same issue? After installing the library and using the Fade animation, Dev tools prints out this error message:
index.js:1 Warning: Legacy context API has been detected within a strict-mode tree.
The old API will be supported in all 16.x releases, but applications using it should migrate to the new version.
Please update the following components: RevealBase
Issue Analytics
- State:
- Created 3 years ago
- Reactions:14
- Comments:14
Top Results From Across the Web
React / Reactstrap Warning: Legacy context API has been ...
I have this same warning, and I fixed it changing in the index.js file, the value of <React.StrictMode> to <React.Fragment> .
Read more >Legacy context API has been detected within a strict-mode tree.
What is happening? Warning: Legacy context API has been detected within a strict-mode tree. The old API will be supported in all 16.x...
Read more >React MDBTabContent Component - Legacy context API has ...
The React sample app with the download gives the following error in strict mode Warning: Legacy context API has been detected within a...
Read more >Reactjs – React / Reactstrap Warning: Legacy context API has ...
Reactjs – React / Reactstrap Warning: Legacy context API has been detected within a strict-mode tree · Best Solution · Related Solutions ...
Read more >Using strict mode in React 18: A guide to its new behaviors
While strict mode has been a React feature for quite some time, ... Warnings on the legacy context API; React v18 unmounting and...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Guys go to index.js and change React.StrictMode to React.Fragement
Yes! I just installed the library and use the Reveal component for custom CSS effects. I get the error you described plus a warning
Warning: componentWillReceiveProps has been renamed, and is not recommended for use. See https://fb.me/react-unsafe-component-lifecycles for details.Here’s a photo: