I have a functional component called (First)
function First() {
const [count,setCount]=useState(0)
console.log(\"component first rendering\") // this lo
This is happening because your App is wrapped under React.StrictMode
.
Strict mode is introduced for functional components in React 16.*. We wrap our component under React.StrictMode
to identify the potential errors in our application.
StrictMode helps to maintain stability of large codebases and helps in up-gradation to newer versions of React. StrictMode logs errors in console for the issues which our application can have:
React.StrictMode needs to trigger some methods and lifecycle hooks twice to resolve these problems:
These are methods which might be called more then once and can have side effects, so React.StrictMode trigger these methods twice to check any side effect. If there is any sideeffect, the error will be logged. (side effect: Things which are updated outside the method/component)
There are possibilities that we are using some old React methods and APIs, So React.StrictMode identifies that and log the error to console mentioning, the method is outdated.
Conclusion: React.StrictMode is provided by React community to help our applications keep track of changes and we can easily upgrade our applications to new versions with Confidence.