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

@dset/data

v1.0.0

Published

DSET data-access layer (Layer: data) — a facade over TanStack Query v5. Consumers use useResource/useMutationResource/createApiClient and never import TanStack directly.

Readme

@dset/data

The DSET data-access layer — a facade over TanStack Query v5 (ADR-0004). Consumers use three primitives and never import @tanstack/react-query directly, so the query engine stays a swappable implementation detail.

Layer rule: data may import only @dset/utils.

Primitives

| Export | Replaces in i3MS | Purpose | | ------------------------------------ | -------------------------------------------- | ---------------------------------------------------------------------------------- | | createApiClient(config) | services/apiClient.js + config/api.js | Typed fetch wrapper: JSON, error extraction, query strings, abort, raw responses | | useResource(options) | useAdminResource(fetcher) | Read facade — { data, loading, error, refetch } + caching/dedup/polling | | useMutationResource(options) | imperative service call + manual refetch() | Write facade with declarative invalidateKeys | | DataProvider / createQueryClient | — | One-time setup with platform defaults |

Setup

import { DataProvider } from '@dset/data';

<DataProvider>
  <App />
</DataProvider>;

Reading data

import { useResource } from '@dset/data';

// The fetcher keeps i3MS's (signal) => Promise<T> shape exactly.
const { data, loading, error, refetch } = useResource({
  key: ['invoices', { month }],
  fetcher: (signal) => api.get('/invoices', { query: { month }, signal }),
});

i3MS compatibility contract

The return shape is identical to useAdminResource{ data, loading, error, refetch }, data is null until loaded, error is a normalized string. So component code that consumes those fields migrates with zero changes. The only delta is in the hook definition: it now takes an explicit, serializable key (which TanStack requires, and which is exactly what unlocks caching, request de-duplication and background refetch). The fetcher signature is unchanged.

Writing data

const { mutate, loading, error } = useMutationResource({
  mutationFn: (gstin: string) => api.put('/transporter/gstin', { gstin }),
  invalidateKeys: [['transporters']], // auto-refetch instead of manual refetch()
});

Design notes

  • TanStack is hidden. Only queryClient.ts, DataProvider.tsx and the two hooks import it. Swapping the engine touches those files alone — no app changes.
  • Errors are normalized. Everything surfaces as an ApiError (status + detail preserved); facades expose a plain string error.
  • Retry policy: never retry 4xx or aborts; retry transient/5xx up to twice.
  • staleTime starts at 0 (parity with i3MS always-fresh fetches); raise it per-resource as caching is validated.