This repository was archived by the owner on Jun 11, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Jun 11, 2026. It is now read-only.
Feature/Maintenance: React.StrictMode Support / Deprecations #605
Description
React is deprecating a bunch of APIs in favor of new/safer ways to do the same things while being more compatible with the upcoming React Suspense / Async Mode.
It'd be great if ReactXP was compatible with Strict-Mode sooner than later!
Details
My app run flags the following:
componentWillMountneeds to be moved to:componentDidMount(orgetDerivedStateFromProps) Used in:- native-common/RootView
- web/ScrollView
- web/listAnimations/MonitorListEdits
- extensions/navigation/src/web/Navigator
componentWillReceivePropsneeds to be moved togetDerivedStateFromPropsUsed in:- native-common/PopupContainerView
- native-common/Button
- native-common/View
- web/View
- windows/View
- web/ViewBase
- web/ScrollView
- macos/TextInput
- native-common/TextInput
- web/TextInput
- web/Image
- web/Animated
- web/RootView
- extensions/virtuallistview/src/VirtualListCell
- extensions/virtuallistview/src/VirtualListView
componentWillUpdateneeds to move to tocomponentDidUpdateorgetDerivedStateFromPropsUsed in:- native-common/View
- web/listAnimations/MonitorListEdits
- common/utils/FocusManager
Activity
erictraut commentedon Jun 19, 2018
ReactXP is intended to run with a wide range of RN versions. Our normal way of dealing with deprecated features in RN is to write conditional logic that attempts to use the new API but falls back on the old API if it's not present. I don't think that technique is possible in this case. For this reason, we may need to stick with the current implementation for a while. Presumably, newer versions of RN will continue to support the classical lifetime methods for a long time, since they're used by so much existing code.
fbartho commentedon Jun 19, 2018
I’ve been doing some research, and in each case I examined, it’s possible to update the code to be backwards compatible, but requires a mix of tweaks. Since some of the current structure exists to support Animation, in some cases different tweaks will be needed.
I’ve been swamped at work, but if our launch goes fine, I was going to make a stab at this in July.
erictraut commentedon Sep 8, 2018
Frederic Barthelemy (@fbartho), any update on this? I'm going to be releasing the next major version of ReactXP soon.
fbartho commentedon Sep 8, 2018
Hi Eric Traut (@erictraut)! We just launched TaskRabbit Client, using ReactXP, on the iOS AppStore this past Tuesday.
I’m currently prepping for Android among other things, but I’m starting so get some of my open source duties done 😉
No active updates, but I still believe this refactor is necessary. I’d love to collaborate on this one if anyone wants to help out.
I feel I don’t have the full experience of ReactXP on the web due to all the RN-only libs we ended up pulling in to launch, but I hope going forwards that will change.
erictraut commentedon Sep 8, 2018
Congrats on the launch! That's no small achievement.
erictraut commentedon Mar 9, 2019
Closing in favor of new issue #1039.
mikehardy commentedon Aug 9, 2019
Eric Traut (@erictraut) this may be worth re-opening with a laser focus on moving to the new APIs. #1039 has 2 PRs associated with it from me now, but they are just handling deprecation warnings / API breaks, they are not handling moving to the recommended new APIs so I don't believe they will actually handle the StrictMode / suspend/async stuff referenced originally here. Or I could be completely mis-reading it