frozencap

@lpil gentle bump, any news on this?

@aLemonFox have you tried removing the previous entry before setting the new one?

@ramirobg94 neither of those cases apply because the calls are _sync_. To be clear that means _not async_.

I don’t think this should be merged, maybe just a doc update. You can just wrap the method yourself.

Again, this is how mmkv is designed. You can wrap the method yourself. Wrapping it lib-level would give new non-mmkv semantics to the lib. To keep it 💯 mmkv, the...

Read this https://github.com/Tencent/MMKV/issues/610

Personally I just wrapped writes with preprended deletes and called it a day. No noticeable difference in write performance. If you're testing against high volume of writes or high write...

@aLemonFox just use this lib and wrap writes with a preprended delete ```js setItem: (key, value) => { storage.delete(key) storage.set(key, value); }, ``` ...or just unsexy `AsyncStorage` whose writes do...

@aLemonFox Btw mmm MMKV is not reactive

> It's not only falsely advertised, it's broken by design. Moving from async to mmkv is like switching to a bmw but that suddenly crashes into a lamp post if...