npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details


  • User packages



Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.


Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner




EXPERIMENTAL - USE WITH CAUTION - Web Storage API for React Native





Build npm version




Web Storage API for React Native.


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


diff --git a/packages/test-app/babel.config.js b/packages/test-app/babel.config.js
index 69ebd557..a012b7f5 100644
--- a/packages/test-app/babel.config.js
+++ b/packages/test-app/babel.config.js
@@ -13,6 +13,7 @@ module.exports = {
           { runtime: "automatic" },
+        [require("@rnx-kit/polyfills")],
diff --git a/packages/test-app/src/App.native.tsx b/packages/test-app/src/App.native.tsx
index 599634a9..b068909a 100644
--- a/packages/test-app/src/App.native.tsx
+++ b/packages/test-app/src/App.native.tsx
@@ -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 {
 } 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 {
@@ -186,6 +187,14 @@ function App({ concurrentRoot }: { concurrentRoot?: boolean }) {

+  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 }) {
         <Header />
+        <View style={}>
+          <Feature value={localValue}>window.localStorage</Feature>
+        </View>
         <View style={}>
           <Button onPress={startAcquireToken}>Acquire Token</Button>


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