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

@quarkhz/query

v0.0.3

Published

Async data for Quark: query, mutation and bindQuery on the signal graph, with abort-aware runs and SSR hydration.

Readme

@quarkhz/query

Async data on the signal graph: query, mutation and bindQuery, with abort-aware runs and SSR hydration.

npm i @quarkhz/query @quarkhz/react @quarkhz/core
import { query } from '@quarkhz/query';

const user = query((id: number) => fetch(`/api/users/${id}`).then((r) => r.json()));

const snap = user.ensure(1); // a signal holding the snapshot; starts the fetch

snap.v.phase; // 'idle' | 'pending' | 'fulfilled' | 'rejected'
snap.v.data;  // the payload once fulfilled
snap.v.error; // the reason once rejected

user(1) reads the cached entry without starting anything; user.ensure(1) starts it if needed. Both return a signal, so any computed, effect or sg.* binding that reads the snapshot updates on its own — the component around it never re-renders.

In JSX

Importing the package registers the sg.query, sg.mutation and sg.bindQuery specials on sg:

import '@quarkhz/query'; // once, at the entry point
import { sg } from '@quarkhz/react';

The registration is deliberately an import side effect. That is why this layer lives in its own package: import { sg } alone no longer drags the async code into the bundle, and a project that never fetches never pays for it.

Do not set "sideEffects": false in a project that re-bundles this package — the bundler would drop the registration and leave sg.query undefined.

Notes

  • Arguments are the cache key. When any argument is an object, array or function, pass options.key explicitly — the package refuses to guess.
  • A superseded run is aborted: getCurrentAsyncAbortSignal() inside a fetcher gives the AbortSignal to hand to fetch.
  • On the server each request gets its own cache, and the client hydrates from it instead of re-fetching.

Links

The source is closed; the published package contains the built dist only.

License

Apache-2.0