parentComponent must be a valid React Component after upgrading to 1.1.0
See original GitHub issueComing from Overlay.js.
Solution: do not upgrade to 1.1.0 when using React 15.
It did not immediately occur to me that version 1.1.0 depends on React 16. And because my package.json states "react-materialize": "^1.0.6", it automatically updates to new minor versions (which should not contain breaking changes).
This caused my project to break with this error.
Shouldn’t the major version be upped to reflect this breaking change? Or is there a way to not automatically update to versions which require a higher version of React?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:3
- Comments:7 (4 by maintainers)
Top Results From Across the Web
Upgraded to React v16, seeing Error: parentComponent must ...
I added a new component to my project via a private NPM package. It has the following dependencies as indicated in my project's ......
Read more >Components and Props - React
This function is a valid React component because it accepts a single “props” (which stands for properties) object argument with data and returns...
Read more >Use React.memo() wisely
1. React.memo(). When deciding to update DOM, React first renders your component, then compares the result with the previous render. If the ...
Read more >When do components update? — reagent 1.1.0 - cljdoc
reagent: A simple ClojureScript interface to React Documentation for ... Answer: when the parent Component re-renders, and supplies a new value as the...
Read more >react-currency-format - npm
React component to format currency in an input or as a text. ... representation of numbers (unformatted) then this should be passed as...
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 Free
Top 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

Thanks! Fortunately I can upgrade to React 16, so that obviously solves the problem also. But others might not be so fortunate.
It is an error.
The error in overlay.js is triggered by just rendering a
Modal. I do not useOverlaymyself. MyModal.jsx:You are absolutely correct. I checked the components but couldn’t find anything broken, that’s why I opted for a minor. I’ll have a look at this ASAP