@react-native-webapis/web-storage
🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧
THIS TOOL IS EXPERIMENTAL — USE WITH CAUTION
🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧🚧
Web Storage API
for React Native.
Installation
yarn add @rnx-kit/polyfills --dev
yarn add @react-native-webapis/web-storage
or if you're using npm
npm add --save-dev @rnx-kit/polyfills
npm add @react-native-webapis/web-storage
Usage
@@ -13,6 +13,7 @@ module.exports = {
{ runtime: "automatic" },
],
[require("@babel/plugin-transform-react-jsx-source")],
+ [require("@rnx-kit/polyfills")],
],
},
],
@@ -1,3 +1,4 @@
+// @react-native-webapis
import { acquireTokenWithScopes } from "@rnx-kit/react-native-auth";
// Both `internal` imports are used to verify that `metro-resolver-symlinks`
// resolves them correctly when `experimental_retryResolvingFromDisk` is
@@ -7,7 +8,7 @@ import {
getRemoteDebuggingAvailability,
} from "internal";
import { getHermesVersion } from "internal/hermes";
-import React, { useCallback, useMemo, useState } from "react";
+import React, { useCallback, useEffect, useMemo, useState } from "react";
import type { LayoutChangeEvent } from "react-native";
import {
NativeModules,
@@ -186,6 +187,14 @@ function App({ concurrentRoot }: { concurrentRoot?: boolean }) {
[setFabric]
);
+ const [localValue, setLocalValue] = useState("Pending");
+ useEffect(() => {
+ const key = "sample/local-storage";
+ window.localStorage.setItem(key, "Success");
+ setLocalValue(window.localStorage.getItem(key) ?? "Failed");
+ return () => window.localStorage.removeItem(key);
+ }, []);
+
return (
<SafeAreaView style={styles.body}>
<StatusBar barStyle={isDarkMode ? "light-content" : "dark-content"} />
@@ -195,6 +204,9 @@ function App({ concurrentRoot }: { concurrentRoot?: boolean }) {
style={styles.body}
>
<Header />
+ <View style={styles.group}>
+ <Feature value={localValue}>window.localStorage</Feature>
+ </View>
<View style={styles.group}>
<Button onPress={startAcquireToken}>Acquire Token</Button>
</View>
Rationale
web-storage
is a new implementation that leverages platform APIs:
Instead of using existing implementations, we opted for this because:
- The semantics and limitations of Web Storage API are very similar to the
platform specific APIs. For instance, you're not supposed to store big data or
you don't expect this data to be cloud-backed. We also get data consistency
and resilience for free.
- SQLite is overkill for a simple key-value store, and comes with its own set of
problems.
- In the past, devs have asked for the backing storage to be accessible from the
native side as well. By using the platform's API, we get this for free.
- With zero external dependencies, the impact on your app size is low.
Not yet implemented
Storage.key()
- None of the implementations guarantee the order of keys, i.e.
key(m)
and
key(n)
can both return the same key. We can probably work around this by
keeping a snapshot. For now, this will remain unimplemented until someone
actually needs it.
storage
event