If you have been using React hooks, specifically useEffect then you may have come across the same problem that I did when making asynchronous calls such as data fetching. I first encountered this when finding a warning in my console:

Warning: Can’t perform a React state update on an unmounted component. React

… when doing something like this:

const [ article , setArticle ] = useState ( null ) ; useEffect ( ( ) => { async function fetchData ( ) { const article = await API . fetchArticle ( id ) ; setArticle ( article ) ; } fetchData ( ) ; } , [ id ] ) ;

This will happen when the component is unmounted before the data is returned. But there is also a separate issue here too; if our id dependency changes while the first fetch is still happening, the effect will run again with the new id and there’s no guarantee that the data will come back in the correct order. Additionally, if the id changed then are we really interested in the value returned from the server any more? The state will still be updated with the old data once the request has returned.

To fix this you may have seen a pattern where the lifecycle of the effect is tracked with a didCancel flag. The call to the state setter is then guarded with this variable.

function Article ( { id } ) { const [ article , setArticle ] = useState ( null ) ; useEffect ( ( ) => { let didCancel = false ; async function fetchData ( ) { const article = await API . fetchArticle ( id ) ; if ( ! didCancel ) { setArticle ( article ) ; } } fetchData ( ) ; return ( ) => { didCancel = true ; } ; } , [ id ] ) ; }

I first found that pattern on Dan Abramov’s blog post and it looks like that pattern came from Robin Wieruch’s blog post. While the examples there call the variable didCancel , really that flag tells us one of a few things:

One of the dependencies of the hook has changed

The component was unmounted

The effect wasn’t passed any dependencies array at all, but you probably aren’t fetching data on each render.

I like this method of tracking the “lifecycle” of the useEffect hook, but feel like that variable could have been included by the React team as part of the interface of useEffect , there’s an empty parameter list passed to the effect right there!

useEffect ( ( ) => { } , [ ] ) ;

I decided to create a custom hook that had a similar interface to the regular useEffect hook, but had this functionality built in.

As I mentioned before, the useEffect hook takes a single parameterless function as the first argument. We can use this fact to our advantage, as any current use of useEffect would not be using the arguments list, so it should be easy to slot this new hook in. We can pass in a parameter that does the same job as the didCancel variable.

This is how I’d like it to look when used:

function Article ( { id } ) { const [ article , setArticle ] = useState ( null ) ; useCancelledEffect ( didCancel => { async function fetchData ( ) { const article = await API . fetchArticle ( id ) ; if ( ! didCancel ) { setArticle ( article ) ; } } fetchData ( ) ; } , [ id ] ) ; }

And here is a quick naïve first implementation:

function useCancelledEffect ( effect , deps ) { useEffect ( ( ) => { let didCancel = false ; effect ( didCancel ) ; return ( ) => { didCancel = true ; } ; } , deps ) ; }

You may notice an issue here. As a javascript boolean is a primitive type, the didCancel variable will be passed by value to the effect function, so when we set the variable to true in the clean up function, its value will not be reflected inside the effect when the asynchronous effect continues.

We can fix this by passing a function that returns the didCancel instead of the variable itself. The definition of the function will capture the isCurrent variable, so when it’s changed, the return value of the function will also be updated. I’m also going to flip the boolean so that it’s true by default (because I think it looks better when used) and change the name to “current”.

function useCurrentEffect ( effect , deps ) { useEffect ( ( ) => { let isCurrent = true ; const checkCurrent = ( ) => isCurrent ; effect ( checkCurrent ) ; return ( ) => { isCurrent = false ; } ; } , deps ) ; }

And now we use it like this:

useCurrentEffect ( isCurrent => { async function fetchData ( ) { const article = await API . fetchArticle ( id ) ; if ( isCurrent ( ) ) { setArticle ( article ) ; } } fetchData ( ) ; } , [ id ] ) ;

What about clean up?

So far our custom hook ignores the return value of the effect, so a returned clean up function won’t be called:

useCurrentEffect ( isCurrent => { async function fetchData ( ) { const article = await API . fetchArticle ( id ) ; if ( isCurrent ( ) ) { setArticle ( article ) ; } } fetchData ( ) ; return ( ) => { API . doSomeCleanup ( ) ; } ; } , [ id ] ) ;

Let’s fix that by taking any returned clean up function and calling it in the outer clean up function:

function useCurrentEffect ( effect , deps ) { useEffect ( ( ) => { let isCurrent = true ; const checkCurrent = ( ) => isCurrent ; const cleanup = effect ( checkCurrent ) ; return ( ) => { isCurrent = false ; cleanup && cleanup ( ) ; } ; } , deps ) ; }

And that’s it. This custom hook has a very similar interface to the original useEffect , but now we can track if the dependencies have changed in any asynchronous callbacks.

Lint rules for our custom hook

After using this hook for a while, I realised that I missed the exhaustive-deps warning I got from eslint when I missed a dependency. Searching around the documentation, I couldn’t find a nice way to get eslint to give me the same warnings I’d get with useEffect . I did find that I could do something like this:

import { useCurrentEffect as useEffect } from "./hooks/useCurrentEffect" ;

This kind of works, but it seems messy and conflicts with when I want to use the regular useEffect .

Eventually I found within the react-hooks/exhaustive-deps source, that you could configure custom hooks in the .eslint config file, with the additionalHooks option. "react-hooks/exhaustive-deps": ["warn", { "additionalHooks": "useCurrentEffect" }], Note: This option takes a regular expression.

Obligatory npm package