Open arshak-grigoryan opened 1 year ago
From #1412, #1275, #835, and #809 can be derived, no, this library is not maintained anymore. Time has moved on, consider using mmkv for persisting your state, see a tutorial here. The first place of the common benchmark of stores says it all.
@ManuelTS thank you for recommending MMKV and even linking a tutorial!
I'd like to add a note for people who run into this in the future: that tutorial recommends using the mmkv
package, which is not at all related. Whenever the author mentions mmkv
, replace it with react-native-mmkv
. Hopefully this saves you some time.
Do you guys have any good alternative for a react website? (not a react native app)
Do you guys have any good alternative for a react website? (not a react native app)
I'm still using the library for a simple use-case without any issues, i.e. it's stable.
I believe @acemarke recently mentioned in an interview that someone is working on a new redux persistance library.
@ckalika I can see there has not been many updates in recent times, which makes me worried as we heavily depend on this library in our project. Do you have plans to continue work on this?
If not, perhaps it is time to either call for anyone willing to pick up maintenance and/or at least mark the project as not being actively maintained.
@Dr-Horv I also work on a large project which uses RTK + redux-persist
+ redux-persist-sensitive-storage
. Both persist and the sensitive storage libaries are no longer being maintained. I still like using RTK, and it continues to be the number 1 react state container ahead of a quickly growing Zustand. It seems to me that the 2 options are either to 1) replace RTK with Zustand + mmkv
for persistance or 2) continue with RTK, replacing redux-persist
with mmkv
.
Luckily my app hasn't been deployed to customer devices yet, so it'd be much easier for me to replace redux-persist
with mmkv
following viniciuspetrachin's tutorial.
@tonyjaimep I haven't been able to get that tutorial to work at all. Do you have an example repo or something? I also had to replace setItem with mmkv.set()
and same for getItem()
.
@rt2zz How's it going?