v3.0.0 - PropTypes warning
See original GitHub issueHey guys. I’ve updated to v3.0.0 and now I see a warning in console:
Warning: Accessing PropTypes via the main React package is deprecated, and will be removed in React v16.0. Use the latest available v15.* prop-types package from npm instead. For info on usage, compatibility, migration and more, see https://fb.me/prop-types-docs
Didn’t check, but I think this change in a couple places is to blame: https://github.com/mzabriskie/react-draggable/commit/e405109dea195e12af7f3c98e646617655b0cf1a#diff-f5848504b1e287185730035e153a214fR2
Can you check, please?
What’s the reason behind such change?
Issue Analytics
- State:
- Created 6 years ago
- Comments:5
Top Results From Across the Web
Better prop types warnings · Issue #279
React prop types warning doesn't reveal info on the component's instance What is the expected behavior? Print also the component's props Wh.
Read more >Still getting PropTypes warning after installing react- ...
Warning: Accessing PropTypes via the main React package is deprecated, and will be removed in React v16.0. Use the latest available v15.
Read more >How to validate React props using PropTypes
Learn how to validate props with React PropTypes, React's internal mechanism for adding type checking to component props.
Read more >prop-types - NPM Package Overview
Runtime type checking for React props and similar objects. Version: 15.8.1 was published by ljharb. Start using Socket to analyze prop-types ...
Read more >How to Use PropTypes in React
Before the release of React 15.5.0, PropTypes were available in the React ... to make sure a warning is shown if the prop...
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

This is fixed in
3.0.3.@STRML thank you!