How to Use the useEffect Hook in React.js

How to Use the useEffect Hook in React.js

React.js, a JavaScript library for building user interfaces, has made a significant impact in the web development community with its adoption of a component-based architecture and its handling of state and lifecycle methods. However, with the introduction of Hooks in React 16.8, React.js has taken a giant leap forward in terms of improving the developer experience. One of the most commonly used Hooks is useEffect, which we will be unpacking in depth in this post on codedamn.

Delving into useEffect

The useEffect hook is a function provided by React that allows you to handle side effects in your functional components. Now, you might be wondering what side effects are. In the context of React.js, side effects are any operations that interact with the outside of the component scope, such as data fetching, subscriptions, timers, console logging, or manually changing the DOM.

Before the introduction of Hooks, these side effects were typically handled inside lifecycle methods when working with class components. But with the advent of Hooks, we can now handle these side effects in functional components using useEffect.

The useEffect hook is analogous to componentDidMount, componentDidUpdate, and componentWillUnmount lifecycle methods rolled into one.

The syntax of useEffect is as follows:

useEffect(() => { // Your side effect here }, [dependencies]);

The useEffect hook takes two arguments: a callback function where you can perform your side effects, and an optional array of dependencies.

Applying useEffect in Practice

To fully grasp how the useEffect hook operates, let's delve into an example where we'll be employing useEffect to fetch data from an API.

import React, { useState, useEffect } from 'react'; import axios from 'axios'; const UserComponent = () => { const [userData, setUserData] = useState(null); useEffect(() => { const fetchData = async () => { const response = await axios.get(''); setUserData(; } fetchData(); }, []); return ( <div> {userData && ( <div> <h1>{}</h1> <p>{}</p> </div> )} </div> ); } export default UserComponent;

In the above code, we're using the axios HTTP client to fetch user data from an API. This fetching operation is a side effect, hence we place it inside the useEffect hook. The empty array [] as the second argument signifies that the effect will only execute once after the initial render, and not on subsequent re-renders.

Dependencies in useEffect

The dependencies of a useEffect hook are the values that the effect relies on. If any of these values change between renders, the effect will be run again.

If you don't specify any dependencies, i.e., if you pass an empty array, the effect will only run once, very similar to the componentDidMount lifecycle method in class components.

On the other hand, if you want the effect to run on every re-render, you can avoid passing the second argument altogether:

useEffect(() => { // Your side effect here });

In this scenario, the effect runs after every render, akin to a combination of componentDidMount and componentDidUpdate.

Cleanup Function in useEffect

Sometimes, your effect might involve setting up some resources that need to be cleaned up before the component unmounts. For instance, if your effect subscribes to a service, you would want to unsubscribe when the component unmounts to avoid memory leaks.

This cleanup process is performed by returning a cleanup function from your effect. When the component unmounts, or before the next time the effect runs, this cleanup function gets executed:

useEffect(() => { // Subscribe to a service const subscription = someService.subscribe(); // Cleanup function return () => { // Unsubscribe from the service someService.unsubscribe(subscription); }; }, [someService]);

Frequently Asked Questions

1. Can I use more than one useEffect in a single component?

Yes, you can use multiple useEffect hooks in one component. This allows you to separate unrelated logic into distinct effects, making your code easier to understand and test.

2. Can useEffect run after every render?

Yes, if you do not provide the second argument when calling useEffect, the effect will run after every render.

3. How can I run an effect only on mount and unmount?

To run an effect only when the component mounts and when it unmounts, you can pass an empty array [] as the second argument to useEffect. This signifies that the effect doesn't depend on any values and should only run on mount and cleanup on unmount.

4. What is a cleanup function in useEffect?

A cleanup function in useEffect is a function that is returned from the effect function. This function cleans up after the effect, for example, by cancelling subscriptions or invalidating timers. It runs before the component unmounts and before subsequent runs of the effect.

For more comprehensive information and advanced scenarios, please refer to the official React.js documentation.

Wrapping Up

To sum it all up, the useEffect hook is a formidable tool at your disposal when working with React.js. It enables you to handle side effects in your functional components, making your code more organized and easier to reason about. Whether you're fetching data, setting up subscriptions, or making manual changes to the DOM, useEffect is up to the task. Happy coding!

Sharing is caring

Did you like what Vishnupriya wrote? Thank them for their work by sharing it on social media.


No comments so far