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

@refinest/context

v0.2.0

Published

Refinest: DAG-based context engine with dependent pickers and reactive store

Readme

@refinest/context

DAG-based context engine for refinest: a reactive store whose slices may depend on one another, with dependent pickers and scope cascading.

Use it for the ambient state a whole admin is filtered by — the selected company, warehouse, product group — where changing one slice must invalidate the slices below it.

Install

pnpm add @refinest/context @refinest/core

Usage

defineContextSlices takes a factory and hands you a builder; each slice's key becomes its name, so it is never written twice:

import { defineContextSlices } from '@refinest/context';

const slices = defineContextSlices((s) => ({
  company: s.static({ value: null }),
  warehouse: s.picker({
    resource: () => warehouseResource,
    dependsOn: ['company'],   // re-resolves when company changes
    resetWhen: ['company'],   // and clears, rather than keeping a stale pick
    persist: 'localStorage',
    required: true,
  }),
}));

Main exports

  • defineContextSlices with defineStaticSlice / defineAsyncSlice / definePickerSlice / defineFromAuthSlice — the four slice kinds: a plain value, an awaited value, a record chosen from a resource, and a value derived from the auth session.
  • createStore / createAtom / createResolver — the reactive primitives underneath.
  • topoSort / trackReads — dependency ordering and read tracking; a slice's dependencies are discovered, not declared twice.
  • mergeScope / cascadeScope / checkRequireScope — merge a parent → child scope chain (child wins) and assert a resource's requireScope is satisfied before querying.

License

MIT