React warns about UNSAFE_componentWillMount in strict mode
Using 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.
Fix it fast
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/2Match what you see, then jump to its fix
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 devConfirmed by legacy.reactjs.org
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/ | head2Fix
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 devConfirmed by legacy.reactjs.org
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 devConfirmed by legacy.reactjs.org
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:
- TaxiDexMy own multi-tenant taxi dispatch SaaS: API, dispatcher portal, driver and passenger apps, and the servers underneath.
- QistLockA NestJS and React SaaS driving an Android Device Owner agent that locks financed phones when payments lapse.
- TaskvareA task and project-management suite: React on the web, Flutter on mobile, TypeScript underneath.
Related fixes
Web apps
Module not found for antd/dist/antd.less after upgrading to Ant Design 5
Module not found: Error: Can't resolve 'antd/dist/antd.less'
Ant Design 5 dropped Less and the bundled CSS file for CSS-in-JS, so antd/dist/antd.less no longer exists.
3 causes, each with a fixWeb apps
Astro Code component fails inside a React component
Astro components cannot be rendered directly via function call
Astro components such as Code only exist on the server and render static HTML.
2 causes, each with a fixWeb apps
React shows Attempted import error when importing a component or function
Attempted import error:
The build found the file but not the name you asked for.
2 causes, each with a fixWeb apps
How to catch and handle a 422 from Axios in a Redux thunk
action.error.message is 'Rejected' and action.payload is undefined
A 422 means the server read the request but cannot process its content, so repeating it unchanged fails again.
4 causes, each with a fixWeb apps
axios gets 429 Too Many Requests from a React app
429 (Too Many Requests)
A 429 comes from the server or an API gateway, not from axios: your client sent too many requests in a window.
4 causes, each with a fixWeb apps
Axios request is not cancelled when a React component unmounts
A cancelled request is logged as an error in the catch block
Axios cancels a request when you pass it an AbortSignal and later call abort() on its controller.
4 causes, each with a fix