Props as read-only data in React - Performance & Optimization

Performance: Props as read-only data

MEDIUM IMPACT

This concept affects how React components update and render, impacting interaction responsiveness and rendering speed.

Passing data to child components without causing unnecessary re-renders

React

function Child({ data }) {
  const newValue = 10; // Use local state or variables instead
  return <div>{newValue}</div>;
}

function Parent() {
  const info = { value: 5 };
  return <Child data={info} />;
}

Props remain immutable, so React can optimize rendering and avoid unnecessary updates.

📈 Performance GainReduces unnecessary re-renders, improving interaction responsiveness (INP).

Passing data to child components without causing unnecessary re-renders

React

function Child({ data }) {
  data.value = 10; // Mutating props directly
  return <div>{data.value}</div>;
}

function Parent() {
  const info = { value: 5 };
  return <Child data={info} />;
}

Mutating props directly causes React to lose track of changes, leading to unpredictable rendering and potential bugs.

📉 Performance CostTriggers extra renders and can cause inconsistent UI updates, increasing INP latency.

Performance Comparison

Pattern	DOM Operations	Reflows	Paint Cost	Verdict
Mutating props inside child	Causes extra DOM updates	Multiple reflows if state changes triggered	Higher paint cost due to unnecessary updates	[X] Bad
Treating props as read-only	Minimal DOM updates	Single reflow when needed	Lower paint cost with optimized rendering	[OK] Good

Rendering Pipeline

When props are treated as read-only, React can efficiently compare previous and new props to decide if a component should re-render, minimizing layout recalculations and paints.

→Reconciliation

→Render

→Commit

⚠️ BottleneckReconciliation stage when props are mutated causing React to re-render unnecessarily

Core Web Vital Affected

INP

This concept affects how React components update and render, impacting interaction responsiveness and rendering speed.

Optimization Tips

1Never mutate props inside a React component; treat them as read-only.

2Use local state or callbacks to handle changes instead of modifying props.

3Immutable props help React optimize rendering and improve interaction responsiveness.

Performance Quiz - 3 Questions

Why should props be treated as read-only in React components?

A To enable direct mutation of parent state from child

B To allow React to optimize rendering and avoid unnecessary re-renders

C To increase the number of DOM updates for better UI feedback

D To reduce the size of the JavaScript bundle

DevTools: React DevTools and Performance panel

How to check: Use React DevTools to inspect component props and state; use Performance panel to record and analyze re-renders and interaction delays.

What to look for: Look for unnecessary re-renders in React DevTools and long interaction delays or multiple layout recalculations in Performance panel.

Practice

1. In React, what does it mean that props are read-only?

easy

A. You cannot change props inside the child component.

B. You can modify props directly in the child component.

C. props are only used for styling components.

D. props are used to store component state.

Solution

1. Step 1: Understand the role of props

   Props are data passed from a parent component to a child component in React.

2. Step 2: Recognize props immutability

   Props are read-only, meaning the child component cannot change them directly.

3. Final Answer:

   You cannot change props inside the child component. -> Option A

4. Quick Check:

   Props are read-only = D [OK]

Hint: Remember: props come from parent, child can't change them [OK]

Common Mistakes:

• Trying to modify props directly inside child component
• Confusing props with state
• Thinking props are for styling only

2. Which of the following is the correct way to access a prop named title inside a functional component?

easy

A. const title = this.props.title;

B. const title = getProps.title;

C. const title = state.title;

D. const title = props.title;

Solution

1. Step 1: Identify functional component syntax

   In functional components, props are passed as a parameter named props.

2. Step 2: Access prop correctly

   You access a prop by props.title. Using this.props is for class components.

3. Final Answer:

   const title = props.title; -> Option D

4. Quick Check:

   Functional component props access = B [OK]

Hint: Use props.parameterName inside functional components [OK]

Common Mistakes:

• Using this.props in functional components
• Confusing state with props
• Trying to use undefined variables like getProps

3. What will be the output of this React component?

function Greeting(props) {
  props.name = "Alice";
  return <h1>Hello, {props.name}!</h1>;
}

// Usage: <Greeting name="Bob" />

medium

A. Hello, Bob!

B. Hello, Alice!

C. Error: Cannot assign to props.name

D. Hello, undefined!

Solution

1. Step 1: Understand props mutability

   Although props are read-only and mutating them is an anti-pattern, JavaScript allows changing the object property within the component function.

2. Step 2: Determine rendered output

   The assignment props.name = "Alice" mutates the value before the return, so the output is "Hello, Alice!".

3. Final Answer:

   Hello, Alice! -> Option B

4. Quick Check:

   Props mutation affects render output = B [OK]

Hint: Mutating props technically works but violates React's read-only principle [OK]

Common Mistakes:

• Thinking props mutation doesn't affect output
• Expecting an error from assignment
• Confusing props with state

4. Identify the error in this React functional component:

function Counter(props) {
  props.count = props.count + 1;
  return <div>Count: {props.count}</div>;
}

medium

A. Props are being mutated directly, which is not allowed.

B. The component should use this.state instead of props.

C. The return statement is missing parentheses.

D. The component should not return JSX.

Solution

1. Step 1: Check for props mutation

   The line props.count = props.count + 1; tries to change props directly, which is not allowed.

2. Step 2: Understand correct data handling

   Props are read-only; to change data, use state or callbacks, not direct mutation.

3. Final Answer:

   Props are being mutated directly, which is not allowed. -> Option A

4. Quick Check:

   Direct props mutation = error = A [OK]

Hint: Never assign to props; use state for changes [OK]

Common Mistakes:

• Trying to mutate props directly
• Confusing props with state usage
• Ignoring React's immutability rules

5. You want to create a component that shows a user's name and allows updating it inside the component. Which approach correctly respects that props are read-only?

hard

A. Modify the props.name directly inside the component to update the name.

B. Use a global variable to store the name and ignore props.

C. Copy props.name to a state variable and update the state to change the name.

D. Pass a new name prop from the child component to the parent.

Solution

1. Step 1: Understand props immutability

   Props cannot be changed inside the component; they are read-only.

2. Step 2: Use state for data that changes

   Copy the prop value to a state variable, then update the state to reflect changes.

3. Final Answer:

   Copy props.name to a state variable and update the state to change the name. -> Option C

4. Quick Check:

   Use state to update data, not props = C [OK]

Hint: Use state for changes, keep props read-only [OK]

Common Mistakes:

• Trying to change props directly
• Using global variables instead of state
• Passing props from child to parent (not possible)