PropTypes is deprecated in React 15.5
See original GitHub issueI was fiddling around upgrading my React project’s packages to their latest versions, including React itself, and as I finished the process and ran npm start
, I’ve got the following warning on the console:
As you can see, the warning is being generated by this component. So I just wanted to let you guys know about this issue.
Cheers
Issue Analytics
- State:
- Created 6 years ago
- Comments:6
Top Results From Across the Web
How to fix React 15.5.3 PropTypes deprecated warning when ...
Warning: Accessing PropTypes via the main React package is deprecated. Use the prop-types package from npm instead. I have already follow the ...
Read more >PropTypes deprecated warnings with React 15.5.0 #75 - GitHub
Hi, any plan to fix the warning with React 15.5.0: Warning: Accessing PropTypes via the main React package is deprecated. Use the prop-types ......
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 >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 ...
Read more >[Solved]-Accessing PropTypes via the main React package is ...
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 use...
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
@caiorg the deprecations have been resolved. Since it was more of an internal/chore type of change, a patch semvar version has been release (0.2.5 -> 0.2.6) It doesn’t a breaking the existing API exposed by this library… that being said, some other libraries and people are experiencing issues with running on version prior to react 15.5 due to how react and prop-types work…
@edward93, as for your issue,
LoginComponent
is the only thing mentioned. Please create a new issue and provide a code example of your issue.@TheSharpieOne Hi sorry for late response. I didn’t have time to look at the comments. Unfortunately I created my own component for that matter and I’m not using this specific one but I will try to test it again and tell you the results if it fails I will open new issue and will share some basic code.