npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

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.

About

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 🙏

© 2026 – Pkg Stats / Ryan Hefner

@ahmetskilinc/sync-react

v0.4.0

Published

React bindings for sync-engine: live queries, index reads, status and rejection surfaces over the local-first client

Readme

@ahmetskilinc/sync-react

React bindings for sync-engine: live queries, index reads, and status/rejection surfaces over the local-first client — with the identity-stability details (useSyncExternalStore snapshot caching, per-model wake-ups, per-group index subscriptions) done once, here, instead of in every app.

npm install @ahmetskilinc/sync-react @ahmetskilinc/sync-client @ahmetskilinc/sync-core

Setup

import { SyncProvider } from "@ahmetskilinc/sync-react";
import { IndexedDBPersistence, SyncClient, WebSocketTransport } from "@ahmetskilinc/sync-client";
import { schema, Thread } from "./schema";

function createClient() {
  const client = new SyncClient({
    schema,
    transport: new WebSocketTransport("wss://app.example.com/api/sync"),
    persistence: new IndexedDBPersistence(`app-${userId}`),
    scope: userId,
  });
  // Define store indexes here, right after construction.
  client.store.defineIndex(Thread, {
    name: "inbox",
    key: (t) => (t.archived ? null : t.folderId),
    compare: (a, b) => b.updatedAt.localeCompare(a.updatedAt),
  });
  return client;
}

<SyncProvider createClient={createClient}>
  <App />
</SyncProvider>;

createClient is called lazily, in the browser only — server rendering gets empty snapshots and never constructs a client.

Hooks

| Hook | Returns | | --- | --- | | useQuery(model, selector?, deps?) | Live records, selector applied outside the subscription | | useRecord(model, id) | One record, identity-stable | | useIndex(model, name, key, { limit, offset }) | One ordered index group; subscribes to that group only | | useSyncStatus() | "offline" \| "connecting" \| "syncing" \| "online" | | useHydrated() | True once persisted state has loaded — gate skeletons on this | | useHasPendingChanges() | True while local writes await confirmation | | useRejections() | Queue of server rejections + dismiss(transactionId) | | usePull(name, args, { enabled }) | Effect-driven named pull with in-flight dedup | | useSyncClient() | The SyncClient, for mutations from event handlers |

All packages move in lockstep — see the repo's MIGRATION.md.