Multiple effects in a component in React - Cheat Sheet & Quick Revision

Recall & Review

beginner

What is the purpose of using multiple useEffect hooks in a React component?

Using multiple useEffect hooks lets you separate different side effects clearly. Each effect can handle a specific task like fetching data, setting up a timer, or updating the document title, making the code easier to read and maintain.

beginner

How does React handle multiple useEffect hooks inside one component?

React runs each useEffect hook independently in the order they appear. This means effects do not block each other and run sequentially after rendering, helping keep logic organized.

intermediate

Why should you avoid combining unrelated side effects into a single useEffect hook?

Combining unrelated side effects makes the code harder to understand and debug. If one effect changes, it might cause unnecessary runs of other effects. Keeping effects separate improves clarity and performance.

intermediate

What happens if two useEffect hooks depend on the same state variable?

Both effects will run when that state changes. React checks dependencies for each effect separately, so each effect reacts only to the changes it cares about.

intermediate

Can you clean up multiple effects separately in React? How?

Yes! Each useEffect hook can return its own cleanup function. React calls these cleanup functions before running the effect again or when the component unmounts, keeping each effect's cleanup isolated.

What is the main benefit of using multiple useEffect hooks in a React component?

A To avoid using state variables

B To run effects in parallel threads

C To reduce the number of renders

D To separate different side effects for clarity

Multiple useEffect hooks help keep side effects separate and clear, improving code readability.

If two useEffect hooks depend on the same state, what happens when that state changes?

A Both effects run independently

B Only the first effect runs

C Neither effect runs

D React throws an error

React runs each effect whose dependencies changed, so both effects run independently.

Where should you place cleanup code for a side effect in React?

A Inside the return function of <code>useEffect</code>

B Outside the component

C In the component's render function

D In a separate component

Cleanup code goes inside the return function of useEffect to run before the effect re-runs or the component unmounts.

What happens if you put unrelated side effects in one useEffect hook?

A Effects run faster

B Code becomes harder to read and debug

C Code becomes easier to maintain

D React merges the effects automatically

Combining unrelated effects makes the code harder to understand and can cause unnecessary effect runs.

In what order does React run multiple useEffect hooks?

A Random order

B Reverse order of appearance

C In the order they appear in the code

D Alphabetical order by variable name

React runs useEffect hooks in the order they appear in the component code.

Explain why using multiple useEffect hooks can improve the clarity and maintainability of a React component.

Think about how separating tasks helps in real life, like organizing tools in different boxes.

Describe how React handles cleanup functions when multiple useEffect hooks are used in one component.

Imagine cleaning up after each task separately before starting it again.

Practice

1. What is the main benefit of using multiple useEffect hooks in a React component?

easy

A. It combines all side effects into one function for faster execution.

B. It separates different side effects for better readability and maintenance.

C. It prevents the component from rendering multiple times.

D. It automatically optimizes the component's performance.

Solution

1. Step 1: Understand the purpose of multiple useEffect hooks

   Multiple useEffect hooks allow you to separate different side effects logically in a component.

2. Step 2: Recognize the benefit of separation

   This separation makes the component easier to read and maintain because each effect handles a specific task.

3. Final Answer:

   It separates different side effects for better readability and maintenance. -> Option B

4. Quick Check:

   Multiple effects = separation and clarity [OK]

Hint: Multiple effects separate tasks for clarity and easier updates [OK]

Common Mistakes:

• Thinking multiple effects combine tasks into one
• Believing multiple effects prevent re-renders
• Assuming multiple effects auto-optimize performance

2. Which of the following is the correct syntax to use two separate useEffect hooks in a React functional component?

easy

A. useEffect(() => { /* effect 1 */ }, []); useEffect(() => { /* effect 2 */ }, []);

B. useEffect(() => { /* effect 1 */ }, []) useEffect(() => { /* effect 2 */ }, []);

C. useEffect(() => { /* effect 1 */ } useEffect(() => { /* effect 2 */ });

D. useEffect(() => { /* effect 1 */ }, [] && []) useEffect(() => { /* effect 2 */ }, []);

Solution

1. Step 1: Recall correct useEffect syntax

   The useEffect hook takes a function and a dependency array as arguments, separated by a comma.

2. Step 2: Identify correct separation of two hooks

   Two separate useEffect hooks should be called one after another, each with its own function and dependency array, ending with semicolons.

3. Final Answer:

   useEffect(() => { /* effect 1 */ }, []); useEffect(() => { /* effect 2 */ }, []); -> Option A

4. Quick Check:

   Separate hooks with own deps and semicolons [OK]

Hint: Each useEffect needs its own function and dependency array [OK]

Common Mistakes:

• Using commas instead of semicolons between hooks
• Combining dependency arrays incorrectly
• Omitting dependency arrays causing unwanted runs

3. Consider this React component code:

function Example({ count }) {
  useEffect(() => {
    console.log('Effect A:', count);
  }, [count]);

  useEffect(() => {
    console.log('Effect B: component mounted');
  }, []);

  return <div>Count: {count}</div>;
}

What will be logged when the component first mounts with count = 5?

medium

A. Effect B: component mounted only

B. Effect B: component mountedEffect A: 5

C. Effect A: 5 only

D. Effect A: 5Effect B: component mounted

Solution

1. Step 1: Understand useEffect execution order on mount

   All useEffect hooks run after the first render. They run in the order they appear in code.

2. Step 2: Identify the order of console logs

   The first useEffect logs 'Effect A: 5', the second logs 'Effect B: component mounted'. So logs appear in code order.

3. Final Answer:

   Effect A: 5
   Effect B: component mounted -> Option D

4. Quick Check:

   Effects run in code order on mount [OK]

Hint: Effects run in code order after first render [OK]

Common Mistakes:

• Assuming effects run in reverse order
• Thinking effects run before render
• Confusing dependency arrays impact on first run

4. What is wrong with this React component using multiple effects?

function Demo({ value }) {
  useEffect(() => {
    console.log('Effect 1:', value);
  }, [value]);

  useEffect(() => {
    console.log('Effect 2');
  });

  return <div>Value: {value}</div>;
}

medium

A. The first useEffect should not have a dependency array.

B. You cannot use two useEffect hooks in one component.

C. The second useEffect has no dependency array, so it runs after every render.

D. The console.log statements are invalid inside useEffect.

Solution

1. Step 1: Check dependency arrays in useEffect hooks

   The first useEffect has a dependency array [value], so it runs only when value changes.

2. Step 2: Analyze second useEffect without dependency array

   The second useEffect has no dependency array, so it runs after every render, which might be unintended.

3. Final Answer:

   The second useEffect has no dependency array, so it runs after every render. -> Option C

4. Quick Check:

   Missing deps means effect runs every render [OK]

Hint: Always add dependency array to control effect runs [OK]

Common Mistakes:

• Thinking multiple useEffects are not allowed
• Ignoring missing dependency arrays
• Believing console.log is invalid inside useEffect

5. You want to fetch user data when the component mounts and also update the document title whenever the user's name changes. How should you organize your useEffect hooks?

hard

A. Use two separate useEffect hooks: one with empty deps for fetch, one with [user.name] for title.

B. Use one useEffect to fetch data and update title together with both dependencies.

C. Use one useEffect with no dependencies to do both tasks on every render.

D. Use two useEffect hooks both with empty dependency arrays.

Solution

1. Step 1: Separate concerns with multiple useEffect hooks

   Fetching data should happen once on mount, so useEffect with empty dependency array is best.

2. Step 2: Update document title when user.name changes

   Use a separate useEffect with [user.name] dependency to update title only when name changes.

3. Final Answer:

   Use two separate useEffect hooks: one with empty deps for fetch, one with [user.name] for title. -> Option A

4. Quick Check:

   Separate effects by task and dependencies [OK]

Hint: Separate effects by when and why they run [OK]

Common Mistakes:

• Combining unrelated tasks in one effect
• Missing dependencies causing stale updates
• Running fetch on every render unintentionally