Warnings: componentWillReceiveProps in strict mode, Legacy context API, findDOMNode is deprecated

This issue is a round-up of multiple past issues documenting the same bug. Feel free to check out the linked issues below for more information. This issue is the source of truth going forward to investigate the issue, report findings, and implement a bug fix.

Issue:

Warning: Using UNSAFE_componentWillReceiveProps in strict mode is not recommended and may indicate bugs in your code. See https://fb.me/react-unsafe-component-lifecycles for details.

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.

Warning: findDOMNode is deprecated in StrictMode. findDOMNode was passed an instance of NodeResolver which is inside StrictMode. Instead, add a ref directly to the element you want to reference. Learn more about using refs safely here: https://fb.me/react-strict-mode-find-node

Issues:

https://github.com/JedWatson/react-select/issues/3751 https://github.com/JedWatson/react-select/issues/3720 https://github.com/JedWatson/react-select/issues/3915 https://github.com/JedWatson/react-select/issues/3745 https://github.com/JedWatson/react-select/issues/4068 https://github.com/JedWatson/react-select/issues/3703

If anyone would like to share any further information, please do so.

[corysimmons]

For anyone else going insane over this, you can disable those warnings (and other, actually helpful ones) by commenting out <React.StrictMode> in index.js. Just remember to uncomment it a few times a day to get the helpful warnings.

---

Update: Stop confused-face’ing me you monsters! 😭

[ljharb]

The UNSAFE removal has been deferred to React 18.