Mounting phase in React - Mini Project: Build & Apply

Understanding the Mounting Phase in React

📖 Scenario: You are building a simple React app that shows a welcome message when the component first appears on the screen.This helps you learn how React sets up components when they are added to the page, called the mounting phase.

🎯 Goal: Create a React functional component that displays a welcome message only once when it first appears.You will set up the component, add a state variable, and use the useEffect hook to run code during the mounting phase.

📋 What You'll Learn

Create a functional React component named WelcomeMessage

Use useState to create a state variable called message initialized to an empty string

Use useEffect with an empty dependency array to set message to 'Hello, welcome to the site!' when the component mounts

Render the message inside a <div> element

💡 Why This Matters

🌍 Real World

React components often need to run code when they first appear, like fetching data or setting up subscriptions. This is called the mounting phase.

💼 Career

Understanding the mounting phase is essential for React developers to manage side effects and initialize components properly.

1

Create the React component and import hooks

Create a functional React component named WelcomeMessage. Import useState and useEffect from 'react'. Inside the component, return a <div> with no content yet.

React

import React, { useState, useEffect } from 'react';

function WelcomeMessage() {
  // Your code here
  return ;
}

export default WelcomeMessage;

Hint

Start by importing the hooks and creating a simple component that returns an empty div.

2

Add a state variable called message

Inside the WelcomeMessage component, use useState to create a state variable named message initialized to an empty string ''.

React

import React, { useState, useEffect } from 'react';

function WelcomeMessage() {
  const [message, setMessage] = useState('');
  // Your code here
  return ;
}

export default WelcomeMessage;

Hint

Use const [message, setMessage] = useState('') to create the state variable.

3

Use useEffect to set the welcome message on mount

Inside the WelcomeMessage component, add a useEffect hook with an empty dependency array []. Inside it, call setMessage with the string 'Hello, welcome to the site!'.

React

import React, { useState, useEffect } from 'react';

function WelcomeMessage() {
  const [message, setMessage] = useState('');

  useEffect(() => {
    // Your code here
  }, []);

  return ;
}

export default WelcomeMessage;

Hint

Remember to pass an empty array as the second argument to useEffect so it runs only once on mount.

4

Render the message inside the <div>

Update the return statement inside WelcomeMessage to render the message state variable inside the <div> element.

React

import React, { useState, useEffect } from 'react';

function WelcomeMessage() {
  const [message, setMessage] = useState('');

  useEffect(() => {
    setMessage('Hello, welcome to the site!');
  }, []);

  return {/* Your code here */};
}

export default WelcomeMessage;

Hint

Use curly braces inside JSX to show the message variable.

Practice

1. What does the mounting phase in React mean?

easy

A. When a component updates due to state change

B. When a component first appears on the screen

C. When a component is removed from the screen

D. When a component re-renders after props change

Solution

1. Step 1: Understand React component lifecycle phases

   The mounting phase is the first phase when a component is created and inserted into the DOM.

2. Step 2: Match the phase to the description

   Mounting means the component appears on screen for the first time, not updates or removal.

3. Final Answer:

   When a component first appears on the screen -> Option B

4. Quick Check:

   Mounting phase = first appearance [OK]

Hint: Mounting means first time component shows [OK]

Common Mistakes:

• Confusing mounting with updating
• Thinking mounting means removal
• Mixing mounting with re-rendering

2. Which of the following is the correct way to run code only once when a React component mounts using hooks?

easy

A. useEffect(() => { /* code */ }, [])

B. useEffect(() => { /* code */ })

C. useEffect(() => { /* code */ }, [state])

D. useEffect(() => { /* code */ }, [props])

Solution

1. Step 1: Recall useEffect dependency array usage

   Passing an empty array [] runs the effect only once on mount.

2. Step 2: Compare options

   useEffect(() => { /* code */ }, []) uses [] so runs once; others run on every render or when dependencies change.

3. Final Answer:

   useEffect(() => { /* code */ }, []) -> Option A

4. Quick Check:

   Empty array means run once on mount [OK]

Hint: Empty array in useEffect runs once on mount [OK]

Common Mistakes:

• Omitting dependency array runs effect every render
• Using state or props array runs effect multiple times
• Confusing useEffect with useState

3. What will be logged to the console when this component mounts?

function Timer() {
  React.useEffect(() => {
    console.log('Timer started');
  }, []);
  return <div>Timer</div>;
}

medium

A. Timer started every render

B. Nothing is logged

C. Timer started

D. Error: useEffect missing dependencies

Solution

1. Step 1: Analyze useEffect with empty dependency array

   The effect runs once on mount, logging 'Timer started' once.

2. Step 2: Confirm no repeated logs or errors

   No dependencies means no repeated logs; no error occurs.

3. Final Answer:

   Timer started -> Option C

4. Quick Check:

   useEffect with [] logs once on mount [OK]

Hint: Empty array means effect runs once on mount [OK]

Common Mistakes:

• Thinking it logs every render
• Expecting no logs without return
• Assuming error due to missing dependencies

4. Identify the error in this React component related to the mounting phase:

function DataFetcher() {
  React.useEffect(() => {
    fetch('/api/data')
      .then(response => response.json())
      .then(data => console.log(data));
  });
  return <div>Loading...</div>;
}

medium

A. Missing dependency array causes fetch on every render

B. fetch is called outside useEffect

C. No return statement in component

D. Cannot use fetch inside useEffect

Solution

1. Step 1: Check useEffect dependencies

   Without a dependency array, useEffect runs after every render, causing repeated fetch calls.

2. Step 2: Identify correct fix

   Adding an empty array [] runs fetch only once on mount, preventing repeated calls.

3. Final Answer:

   Missing dependency array causes fetch on every render -> Option A

4. Quick Check:

   No [] means effect runs every render [OK]

Hint: Always add [] to run effect once on mount [OK]

Common Mistakes:

• Forgetting dependency array in useEffect
• Thinking fetch outside useEffect is needed
• Assuming useEffect cannot contain async calls

5. You want to fetch user data only once when a component mounts and store it in state. Which code correctly implements this mounting phase behavior?

function UserProfile() {
  const [user, setUser] = React.useState(null);

  // Which useEffect is correct?

  A) React.useEffect(() => {
       fetch('/user')
         .then(res => res.json())
         .then(data => setUser(data));
     }, []);

  B) React.useEffect(() => {
       fetch('/user')
         .then(res => res.json())
         .then(data => setUser(data));
     });

  C) React.useEffect(() => {
       fetch('/user')
         .then(res => res.json())
         .then(data => setUser(data));
     }, [user]);

  D) React.useEffect(() => {
       fetch('/user')
         .then(res => res.json())
         .then(data => setUser(data));
     }, [setUser]);

  return user ? <div>{user.name}</div> : <div>Loading...</div>;
}

hard

A. useEffect with setUser dependency causing repeated fetch

B. useEffect without dependencies fetching every render

C. useEffect with user dependency causing infinite fetch

D. useEffect with empty array to fetch once on mount

Solution

1. Step 1: Understand useEffect dependencies for fetching

   Empty array [] runs effect once on mount; no dependencies cause repeated fetches.

2. Step 2: Analyze each option

   The useEffect with an empty dependency array fetches data only once on mount. Without any dependency array, the effect runs after every render. Depending on user causes an infinite loop since updating user triggers re-renders. Depending on setUser runs only once because setUser is stable, but it is unnecessary and may cause ESLint warnings.

3. Final Answer:

   useEffect with empty array to fetch once on mount -> Option D

4. Quick Check:

   Empty [] means fetch once on mount [OK]

Hint: Empty array in useEffect fetches once on mount [OK]

Common Mistakes:

• Leaving out dependency array causes infinite fetch
• Using state as dependency causing loops
• Misunderstanding stable functions as dependencies