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.
Warning: Legacy context API has been detected within a strict-mode tree.
See original GitHub issue`Learn more about this warning here: https://fb.me/react-legacy-context
in RevealBase (created by Slide)
in Slide (at App.js:44)
in nav (at App.js:33)
in header (at App.js:32)
in Header (at src/index.js:9)
in StrictMode (at src/index.js:8)
`
Re-installed react-reveal and still have this error
Issue Analytics
- State:
- Created 3 years ago
- Reactions:11
- Comments:26
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.
Warning : Legacy context API has been detected within a strict-mode tree. The old API will be supported in all 16.x releases, but...
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 >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 >Legacy Context - React
The legacy context API will be removed in a future major version. Use the new context API introduced with version 16.3. The legacy...
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
@jgil-r That does not fix the issue. It just hides it.
Is there a way to ignore this error?