How to call useEffect React Hook on a component mount and unmount

Article autor
April 18, 2020
How to call useEffect React Hook on a component mount and unmount
Elixir Newsletter
Join Elixir newsletter

Subscribe to receive Elixir news to your inbox every two weeks.

Oops! Something went wrong while submitting the form.
Elixir Newsletter
Expand your skills

Download free e-books, watch expert tech talks, and explore open-source projects. Everything you need to grow as a developer - completely free.

Table of contents

With pure function React Components you're not allowed to use lifecycle methods like componentDidMount or componentWillUnmount.

These can be replaced with proper use of useEffect hook introduced in React version 16.8.

Here is the code that will run exactly once when a component is mounted and exactly once when it's supposed to be unmounted:

import { useEffect } from "React";

const ExampleComponent = () => {
  useEffect(() => {
    // Here goes the code you wish to run on mount

    return () => {
      // Here goes the code you wish to run on unmount
    }
  }, []);

  ...
}

It's crucial to pass an empty array as the second argument of useEffect function call. If you omit it or pass dependencies inside of array it won't work as intended.

Work with a team that keeps learning and building better software every day.

Related posts

Dive deeper into this topic with these related posts

No items found.

You might also like

Discover more content from this category

How to safely handle related database operations with Ecto Multi

Sometimes you need to do some database operations at once. A simple example: User-A transfers money to User-B. Updating just one balance at the time creates a risk of data desynchronization. What if the first DB operation goes well but updating the second user’s data fails? Sounds like a hard to catch vulnerability.

How to copy and paste within a terminal in macOS or Linux?

Sometimes we want to store some piece of information while using a terminal, for example, a result of an executed command. We usually save it into some temporary file which is going to be deleted after all. There’s a better way.

Manually update Apollo cache after GraphQL mutation

Ensuring that GraphQL mutations properly update your Apollo client's cache can be a bit tricky - here's how to manually control that.