Context:

When users are loading multiple copies of React, it commonly causes this error:
https://facebook.github.io/react/warnings/refs-must-have-owner.html

We theorize that this may be triggered by different versions of React being required for libraries depending on React. As libraries update to support version 16, this may come up more commonly than in the past.

At the very least, it seems common enough now to be worth fixing, with 300+ issues open across various libraries: https://github.com/search?q=%22Refs+must+have%22&type=Issues&utf8=%E2%9C%93

Folks on this issue are helping out with more info about how to reproduce and debug this state: facebookarchive/draft-js#296

Plan:
MVP:

Add a warning for any time that multiple copies of React are loaded.
Link to documentation about how/why this might happen and how to fix it.

Bonus:

Indicate multiple copies of React with the devtools icon
(?) Add a work-around in the code itself such that React itself will work ok even when you have loaded multiple copies. -> We might not want to do this, since it allows users to continue in a "broken" state.

String Refs Without An Owner Should Fail Gracefully #9962

Description

Metadata

Metadata

Assignees

Labels

Type

Fields

Projects

Milestone

Relationships

Development

Issue actions