React v16.9 support
See original GitHub issuecomponentWillMount is deprecated with warnings now in 16.9.
Here is the warning that is emitted: react-dom.development.js:12050 Warning: componentWillMount has been renamed, and is not recommended for use. See https://fb.me/react-async-component-lifecycle-hooks for details.
- Move code with side effects to componentDidMount, and set initial state in the constructor.
- Rename componentWillMount to UNSAFE_componentWillMount to suppress this warning in non-strict mode. In React 17.x, only the UNSAFE_ name will work. To rename all deprecated lifecycles to their new names, you can run
npx react-codemod rename-unsafe-lifecycles
in your project source folder.
Please update the following components: Media
Issue Analytics
- State:
- Created 4 years ago
- Reactions:8
- Comments:6
Top Results From Across the Web
React v16.9.0 and the Roadmap Update
Today we are releasing React 16.9. It contains several new features, bugfixes, and new deprecation warnings to help prepare for a future ...
Read more >What's New in React Version 16.9 - GrapeCity
With every new release comes some notable bugfixes. Here is a list of the fixes coming from the v16.9 React release: There is...
Read more >16.9.0 - react - npm
React is a JavaScript library for building user interfaces.. Latest version: 18.2.0, last published: 6 months ago. Start using react in your ...
Read more >New Features in React 16.9.0 - Telerik
But now in this new version 16.9 there is support for asynchronous functions, ... React v16.9.0 is available on the npm registry.
Read more >Learn about React v16.9 updates - LinkedIn
Follow this link for more details on act(). One limitation with this utility was that it was supporting only synchronous functions. Because of ......
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
Hi 👋,
Reason it’s an behind the
@next
flag is because I wanted to make sure some people tested this out in the wild before publishing a minor version bump. Since it’s a minor bump, depending on the setup people have they might auto upgrade to this version without realizing. This should be fine, it’s a minor upgrade, so it should be backwards compatible, but I wanted to make sure before publishing.I guess by now enough people have tested it (judging from the 👍’s in this thread), I’ll try to publish this on mainline soon.
Please have a look at the next release: