Element ref was specified as a string (value0) but no owner was set. You may have multiple copies of React loaded. (details: https://fb.me/react-refs-must-have-owner)
See original GitHub issueAre you asking a question?
No, just a proposal
Are you reporting a bug or runtime error?
Yes. all error just after I upgrade react to version 16.
Element ref was specified as a string (value0) but no owner was set. You may have multiple copies of React loaded. (details: https://fb.me/react-refs-must-have-owner).
My code is here:
<Select
name="foo"
value={this.state.input.get('foo')}
options={fooOptions}
placeholder="foo"
onChange={this.metaUpdateInput('foo')}
/>
and I review this repo, notice this line may occur this error:
ref={'value' + index}
React 16, React-Select 1.0.0-rc.10
Issue Analytics
- State:
- Created 6 years ago
- Reactions:5
- Comments:20 (1 by maintainers)
Top Results From Across the Web
Refs Must Have Owner Warning - React
Element ref was specified as a string (myRefName) but no owner was set. You may have multiple copies of React loaded. (details: https://fb.me/react-refs-must- ......
Read more >React JS: Element ref was specified as a string (inner) but no ...
You may be adding a ref to a component that was not created inside a component's render method 3. You have multiple copies...
Read more >react-to-print - npm
So you've created a React component and would love to give end users the ability to print out the contents of that component....
Read more >React Stripe.js reference | Stripe Documentation
Learn about React components for Stripe.js and Stripe Elements. ... You can use Elements with any Stripe product to collect online payments.
Read more >Everything You Need to Know About Refs in React
Short for “reference”, refs are a way to access underlying DOM elements in a React component. There are many reasons why you would...
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 FreeTop 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
Top GitHub Comments
I finally resolved this by making an edit in my webpack setup to specifically state where to use the required version of react. Something similar to the following, with an alteration to the node modules path, will hopefully help some people:
resolve: { alias: { 'react': path.resolve(__dirname, '../../node_modules', 'react') } }
I have the same problem !!