JIYIK CN >

Current Location:Home > Learning > WEB FRONT-END > React >

Rendered fewer hooks than expected error in React

Author:JIYIK Last Updated:2025/03/15 Views:

When we use a hook after a condition that might return a value, we get the error “Rendered fewer hooks than expected. This may be caused by an accidental early return statement.” To fix the error, you need to move all React hooks above any condition that might return a value.

First, let's look at an example that produces this error

import {useEffect, useState} from 'react';

export default function App() {
  const [counter, setCounter] = useState(0);

  // 可能在下面的钩子运行之前返回一个值
  if (counter > 0) {
    return <h1>Hello world</h1>;
  }

  // Rendered fewer hooks than expected.
  // This may be caused by an accidental early return statement
  const [message, setMessage] = useState('');

  return (
    <div>
      <button onClick={() => setCounter(counter + 1)}>Increment count</button>
    </div>
  );
}

The problem in your code snippet is - we use a second useState hook after the conditional that might return a value.

To fix this error, we can only call React hooks at the top level.

import {useEffect, useState} from 'react';

export default function App() {
  const [counter, setCounter] = useState(0);

  // 将钩子移到可能返回的条件之上
  const [message, setMessage] = useState('');

  // 任何可能返回的条件都必须低于所有钩子
  if (counter > 0) {
    return <h1>Hello world</h1>;
  }

  return (
    <div>
      <button onClick={() => setCounter(counter + 1)}>Increment count</button>
    </div>
  );
}

We move the second useState hook above the conditional that might return a value.

This fixes the error since we have to make sure that the React hooks are called in the same order every time we render the component.

This means that we are not allowed to use hooks in loops, conditionals or nested functions.

We have to make sure that all React hooks in our component are called in the same order on every render.

We should never call hooks conditionally.

import {useEffect, useState} from 'react';

export default function App() {
  const [counter, setCounter] = useState(0);

  if (counter > 0) {
    // Error - useEffect is called conditionally
    useEffect(() => {
      console.log('hello world');
    }, []);
  }

  return (
    <div>
      <button onClick={() => setCounter(counter + 1)}>Increment count</button>
    </div>
  );
}

The code snippet in the example will result in an error because the useEffect hook is called conditionally.

To fix this, we can move the if statement into the useEffect hook.

import {useEffect, useState} from 'react';

export default function App() {
  const [counter, setCounter] = useState(0);

  useEffect(() => {
    if (counter > 0) {
      console.log('hello world');
    }
  }, [counter]);

  return (
    <div>
      <button onClick={() => setCounter(counter + 1)}>Increment count</button>
    </div>
  );
}

Moving the if statement inside the hook helps because the hook is now top-level and has predictable behavior, allowing React to correctly preserve state between useState and useEffect calls.

As the documentation states:

  • Only call hooks at the top level
  • Do not call hooks in loops, conditionals, or nested functions
  • Always use hooks at the top level of a React function, before any early returns
  • Hooks are only called from React function components or custom hooks.

This helps React preserve the state of the hook between multiple useState and useEffect calls.

The error "Rendered fewer hooks than expected. This may be caused by an accidental early return statement" means that we rendered more hooks on the first render of the component than on re-renders. This is caused by conditionally returning before using the hook.

To fix the error, you need to make sure you move your hook to the top level of your component and put any conditionals that might return prematurely at the bottom.

For reprinting, please send an email to 1244347461@qq.com for approval. After obtaining the author's consent, kindly include the source as a link.

Article URL:

Related Articles

Fix Uncaught ReferenceError: useState is not defined in React

Publish Date:2025/03/15 Views:142 Category:React

When we use the useState hook in our code but forget to import it, it generates the error Uncaught ReferenceError: useState is not defined. To fix this error, you need to import the hook before using it import {useState} from react . // ?️

React error Uncaught ReferenceError: process is not defined solution

Publish Date:2025/03/15 Views:117 Category:React

To resolve the “Uncaught ReferenceError: process is not defined” error in React, open a terminal in the root directory of your project and update the version of the `react-scripts` package by running `npm install react-scripts@latest` and reinstal

React Error Property 'X' does not exist on type 'Readonly<{}>'

Publish Date:2025/03/15 Views:140 Category:React

The React.js error “Property does not exist on type 'Readonly'” occurs when we try to access the props or state of an untyped class component. To fix the error, you need to use generics on the React.Component class to type the props or state of th

Fix the value prop on input should not be null error in React

Publish Date:2025/03/15 Views:142 Category:React

The warning "value prop on input should not be null" is caused when we set the initial value of an input to null or override the initial value setting it to null, e.g. from an empty API response. Use a fallback value to solve this problem.

Property does not exist on type 'JSX.IntrinsicElements' error in React

Publish Date:2025/03/15 Views:189 Category:React

When the name of a component starts with a lowercase letter, an error "Property does not exist on type 'JSX.IntrinsicElements" will appear. To fix this error, you need to make sure you always start your component names with an uppercase letter, instal

Scan to Read All Tech Tutorials

Social Media
  • https://www.github.com/onmpw
  • qq:1244347461

Recommended

Tags

Scan the Code
Easier Access Tutorial