"Proposal: Lifecycle support for prop-driven side-effects without re-render"

[code76kb]

In class components, UNSAFE_componentWillReceiveProps allows developers to respond to every prop update, even if the update does not cause a re-render. This is crucial for scenarios where props are used as control signals for side-effects (e.g., triggering animations, API calls, or hardware events) without being directly used in render.

Modern alternatives like getDerivedStateFromProps and componentDidUpdate either:

Lack access to this (static method) or

Only trigger after a render, leaving “blind spots” for prop-driven side-effects.

This gap makes it difficult to migrate safely from UNSAFE_componentWillReceiveProps in real-world apps where props carry non-render data flow.

[kraenhansen]

What's the alternative / idea here? Also - this seems like a topic more suitable for a more general React discussion?

[code76kb]

I don't know on alternative yet, right now I'm just concerned about 'UNSAFE_componentWillReceiveProps', i think sooner or later they gonna drop this, I found this very useful in my every app setup,
the purpose of raising this ticket to get this in light
so maybe the expert can come up with something on this