PropTypes via the main React package is deprecated
See original GitHub issueHello, In 3.3.0, in SelectRowHeaderColumn proptypes defined as
SelectRowHeaderColumn.propTypes = {
children: _react.PropTypes.node,
rowCount: _react.PropTypes.number
};
It causes Deprecation warning on React:
Warning: Accessing PropTypes via the main React package is deprecated. Use the prop-types package from npm instead.
React recommends to use prop-types npm package: https://facebook.github.io/react/docs/typechecking-with-proptypes.html
Issue Analytics
- State:
- Created 6 years ago
- Reactions:2
- Comments:16 (8 by maintainers)
Top Results From Across the Web
Accessing PropTypes via the main React package is deprecated
Since the release of React v15.5.0 React.PropTypes is deprecated and has moved to another library. You should use npm install prop-types and ...
Read more >Warning: Accessing PropTypes via the main React ... - GitHub
Strangely, I'm getting this error. Warning: Accessing PropTypes via the main React package is deprecated. Use the prop-types package from ...
Read more >React.PropTypes Is Dead, Long Live PropTypes in React
As of React v15.5 PropTypes are deprecated in the React package and have been given a package of their own. Change is an...
Read more >Warning: Accessing PropTypes via the main React ... - Laracasts
What is this error? Warning: Accessing PropTypes via the main React package is deprecated. Use the prop-types package from npm instead. content.js:5025.
Read more >Don't Call PropTypes Warning - React
In this case, ThirdPartyPropTypes.deprecated is a wrapper calling PropTypes.bool . This pattern by itself is fine, but triggers a false positive because React ......
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
@AllenFang I think the dist files were not updated when v4.0.0-beta-6 (and 5) were commited. I checked and they still have
React.PropTypes
in them, you might not be seeing the warnings because you are running via a build system, but when I try depending on this commit I do get the warning.It was fixed on
v4.0.0-beta.5
and ETA may in the second or third week on June