Maaz Zindani

Loading the index…

↑↓ move↵ openesc close4072 pages
Next.js and React

React warns about UNSAFE_componentWillMount in strict mode

ErrorUsing UNSAFE_componentWillMount in strict mode is not recommended and may indicate bugs in your code.

Short answer

React Strict Mode flags componentWillMount and UNSAFE_componentWillMount because they can run more than once in async rendering. The warning lists the component. Move initial state to the constructor, and move data requests and subscriptions to componentDidMount, with cleanup in componentWillUnmount.

  • Applies to React 18, React 19 class components
  • Updated
  • By Maaz Zindani, Senior Software Engineer

Fix it fast

  1. 1Find out which cause you have

    Read the lines the warning prints after the message. They list the components that use the method. Find each one.

    grep -rn "componentWillMount" src/
  2. 2Match what you see, then jump to its fix

    1. 1The body of componentWillMount calls this.setState or assigns from props.The method only sets up initial stateFix
    2. 2componentWillMount calls an API or loader.The method starts a data requestFix
    3. 3componentWillMount calls subscribe or addEventListener.The method adds a listener or subscriptionFix

What does the error look like?

  • Using UNSAFE_componentWillMount in strict mode is not recommended and may indicate bugs in your code.

Cause 1 of 3

The method only sets up initial state

1Check

Look for state that depends on props and is set once before the first render.

grep -rn -A6 "componentWillMount" src/

2Fix

Initialise state in the constructor.

class Panel extends React.Component {
  constructor(props) {
    super(props);
    this.state = { color: props.defaultColor, palette: 'rgb' };
  }
}

3Verify

Run the app in development. That component is no longer listed in the warning.

npm run dev

Confirmed by legacy.reactjs.org

Did this fix it?

Cause 2 of 3

The method starts a data request

1Check

A request started here can fire more than once and can finish after the component is gone.

grep -rn "fetch\|axios" src/ | head

2Fix

Start the request in componentDidMount and cancel it in componentWillUnmount.

componentDidMount() {
  this._request = loadMyAsyncData().then(data => {
    this._request = null;
    this.setState({ externalData: data });
  });
}
componentWillUnmount() {
  if (this._request) this._request.cancel();
}

3Verify

The warning for that component disappears and data still loads.

npm run dev

Confirmed by legacy.reactjs.org

Did this fix it?

Cause 3 of 3

The method adds a listener or subscription

1Check

Look for calls that need a matching removal.

grep -rn "subscribe\|addEventListener" src/

2Fix

Subscribe in componentDidMount and unsubscribe in componentWillUnmount.

componentDidMount() {
  this.props.dataSource.subscribe(this.handleChange);
}
componentWillUnmount() {
  this.props.dataSource.unsubscribe(this.handleChange);
}

3Verify

No warning, and no duplicate listeners after a remount.

npm run dev

Confirmed by legacy.reactjs.org

Did this fix it?

How do I stop it coming back?

  • Write new components as function components, so these lifecycles never come up.
  • Keep React.StrictMode on in development to catch these early.

Sources

How was this page made?

I drafted this page with AI assistance from the official documents listed under Sources. Every cause above names the document that confirms it. I have not reproduced this fix on a machine of my own yet, so read it as documented guidance, not a test report. Found a mistake? Tell me.

Which stack is behind this page?

Projects of mine built on the same technologies:

Related fixes

Next step

Want this handled for good?

I look after servers, apps and releases end to end. Tell me what keeps breaking.