Error: addComponentAsRefTo(...)
See original GitHub issueHi!
After a long search I found this nice file browser. When I try to include it into my project the following error occures:
Uncaught Error: addComponentAsRefTo(…): Only a ReactOwner can have refs. You might be adding a ref to a component that was not created inside a component’s render
method, or you have multiple copies of React loaded (details: https://fb.me/react-refs-must-have-owner).
Maybe I used the component in the wrong way. I checked if react was loaded multiple times, but I was not successful. All other workarounds like “npm ls” did not work either .
I would be really thankful for any help!
Greetz
Stefan
Issue Analytics
- State:
- Created 6 years ago
- Comments:12 (4 by maintainers)
Top Results From Across the Web
Issues - GitHub
Uncaught Error: Invariant Violation: addComponentAsRefTo(...): Only a ReactOwner can have refs. You might be adding a ref to a component that was not...
Read more >reactjs - addComponentAsRefTo error when using component ...
I do a nmp link in the storybook in order to use it in my project. I can see the component, but it...
Read more >Developers - Error: addComponentAsRefTo(...): Only a ReactOwner ...
Error : addComponentAsRefTo(...): Only a ReactOwner can have refs. You might be adding a ref to a component that was not created inside...
Read more >Fixing the Jest Error, "Invariant Violation
Jest sometimes fails with an error, "Invariant Violation: addComponentAsRefTo". This how-to discusses a solution for the error & speculates ...
Read more >Error Decoder - React - Meta Open Source
The full text of the error you just encountered is: addComponentAsRefTo(...): Only a ReactOwner can have refs. You might be adding a ref...
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
@sichvoge this isn’t my repository 😃 releasing a new version is something that’s up to @bor3ham or @aidanlister I presume
@jonjomckay any plans to release it on npm? unfortunately, there is no
dist
folder so that it will work to reference the github repo in package.json