React 15.5 and 16 deprecation warnings
See original GitHub issueHere is deprecation warning.
Warning: Swipeable: React.createClass is deprecated and will be removed in version 16. Use plain JavaScript classes instead. If you're not yet ready to migrate, create-react-class is available on npm as a drop-in replacement.
So any plans to refactor PropTypes and createClass before new React version coming?
Issue Analytics
- State:
- Created 6 years ago
- Reactions:4
- Comments:5
Top Results From Across the Web
React v15.5.0 – React Blog
New Deprecation Warnings ... If your app produces zero warnings in 15.5, it should continue to work in 16 without any changes.
Read more >Disable React.createClass and PropTypes deprecated ...
Warning : Uncontrolled(Dropdown): React.createClass is deprecated and will be removed in version 16. Use plain JavaScript classes instead. If you ...
Read more >Workaround React deprecation warnings - Memory Spills
It turns out that starting from React v15.5.0, the old way of accessing React.PropTypes and React.createClass has been deprecated. A quick workaround is...
Read more >Disable React.createClass and PropTypes deprecated ...
React 15.5.0 contain new warnings belong to the changes that are coming on React 16, the warning that you are getting, is actually...
Read more >Lessons from migrating a large codebase to React 16 - Discord
Since most libraries have only fixed their issues once the deprecation warnings showed up in React 15.5+, only their most recent version will ......
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
@serheyShmyg I’ve done a bunch of research and asked a few other open source maintainers and the consensus seems to be when you drop support, ala removing react v12 and v13 from peer-deps, that requires a major bump.
I too was hoping to avoid the major bump.
Example of major due partially to dropping support: https://github.com/reactjs/react-redux/releases/tag/v4.0.0
I’m also proposing a major change anyways, #69
nice warning, I wanted to combo
extend React.Component
and HOC capabilities to a major version release soon. i may try to get this out in the next couple of weeks.Looks like we already got a PR for the warning, #64 , woo!