Errors in <StrictMode />

Question

Errors in <StrictMode />

nhardy opened this issue 6 years ago · comments

The component lifecycle componentWillMount will be deprecated in a future 16.x version of React and removed in React 17. This blog post explains more.

The legacy context API will also be removed in React 17, replaced with the new context API introduced in 16.3.

findDOMNode is also deprecated. This blog post explains more.

These three APIs currently log errors when rendered in a <StrictMode /> tree, and are a blocker for React's Concurrent Mode.

Shirshendu Bhowmick · Answer 1 · Sun Sep 01 2019 17:43:24 GMT+0800 (China Standard Time)

Use of deprecated lifecycle methods have been removed in v6.2.0

@nhardy Would like to send PR for findDOMNode and lgeacy context API ?

Nathan Hardy · Answer 2 · Tue Sep 03 2019 14:20:39 GMT+0800 (China Standard Time)

Happy to take a look if I get some time.

Shirshendu Bhowmick · Answer 3 · Tue Sep 03 2019 14:24:27 GMT+0800 (China Standard Time)

Sure let me know.

Nathan Hardy · Answer 4 · Fri Dec 13 2019 06:32:49 GMT+0800 (China Standard Time)

Going to also take a look at #93 which should remove the dependency on ReactDOM.findDOMNode() and close out the remaining issue not already addressed in #110. Unfortunately, React.forwardRef() is a backwards-incompatible API and would mean we would need to bump the peerDependencies for react/react-dom to 16.3.0.