Avoid Deprecated React APIs with React.StrictMode
React has deprecated some APIs in favor of new approaches that will better support the future, concurrent model for rendering. These deprecated APIs will eventually be removed, so it makes sense to avoid them in new code and move away from them in existing code. In this lesson, we’ll wrap our boilerplate application in the StrictMode component and see it in action.
Instructor: [00:00] I've added this componentWillMount method to this App component. Let's see what happens when we do an npm run lint.
[00:09] We're going to see that when we run lint against this, we're going to get two errors. One is for the unexpected console statement. The other one is telling us that componentWillMount is deprecated since React 16.3. This is coming from a React ESLint plugin. It is telling us that we can use unsafe as a prefix for this to clear up this linting error.
[00:30] Let's get the terminal out of the way. Let's prefix this with that unsafe_ and save it. Now if I do another npm run lint, it'll fail again, but this time just for the console statement. As far as our React code is concerned, the linter is happy with it.
[00:52] To make sure that we don't have something like this buried deep in our component tree that will prevent us from using future features, I'm going to go into the index.js file. I'm going to update this. I'm going to actually wrap this entire App component in a component called React.StrictMode.
[01:16] Now that we've added StrictMode, let's see what happens. I'm going to come in here. I'm going to do an npm run dev to run this in a browser.
[01:31] Everything looks fine in our application. I'm going to expand the dev tools. When we look at the console, we're going to see our console that is in our componentWillMount. We're going to get this warning that an unsafe life cycle method was found.
[01:45] StrictMode is going to give us these warnings for anything that's in our tree that's been deprecated. The other thing that's nice about this is that this only happens in development mode. If we go back to our code and we stop dev mode and I do an npm run build to get a production build of this application, I can open that from dist.
[02:12] Now when I look at the console here, we're still going to get our console.log from our componentWillMount life cycle hook, but we're not going to get that warning anymore. That warning is strictly for dev mode.
[02:24] Now if I come back here and I go in and I remove this and then I do an npm run dev again, we'll see that our application still works. When I look in the console, we don't have any logs or any warnings.
[02:45] This component, as long as it doesn't find any issues down the tree, it isn't really going to have any impact on our output. Now we can rely on this React.StrictMode component to warn us if anything within our application is using one of these deprecated life cycle methods.
I'm not getting the error about componentWillMount being deprecated. Using react 16.7.0
No get the error message about componentWillMount of using react16.8.2 version, too.
This is because you need to be using 17 and above to get the error.
I only get the deprecation error when I remove settings: {react: {version: 'xx.xx.x'}} from .eslintrc.json.
So, should we add react {version: 'xx.xx.x'} or not ?
This is working settings for legacy features like componentWillMount
"settings": {
"react": {
"version": "16.999.0"
}
},
For now life-cycle methods are just legacy, not deprecated https://github.com/yannickcr/eslint-plugin-react/pull/1750#issuecomment-425975934