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

@minsize/state

v0.0.1

Published

SolidJs state and cache

Downloads

3

Readme

State

npm version

npm i @minsize/state

yarn add @minsize/state

Getting Started

Atom

An atom represents a piece of state. Atoms can be read from and written to from any component. Components that read the value of an atom are implicitly subscribed to that atom, so any atom updates will result in a re-render of all components subscribed to that atom:


import { atom } from "@minsize/state";

const EXAMPLE_ATOM = atom<{ name: string }, { userId: number }>({
  default: { name: "NAME" }, // default value
  onRequested: (options, key) => {
    console.log(options.userId, key)
  },
  onUpdate: ({ prev, next }, key) => {
    console.log({ prev, next }, key)
  },
})

setter

This is the function that updates the atom, initializes the render of components subscribed to the mutable state. Does not require use in functional components.

import { produce } from "solid-js/store"
import { setter, useAtom } from "@minsize/state"

const COUNT = atom({
  default: {
    user: {
      first_name: "NAME",
    },
  },
})

const App = () => {
  const [state, setState] = useAtom(COUNT)

  const handleClick = () => {
    setter(
      COUNT,
      "user",
      produce((user) => {
        user.first_name = "NAME2"
        return user
      }),
    )
    // OR
    setter(COUNT, "user", "first_name", "NAME2")
  }

  return <div onClick={handleClick}>{state.user.first_name}</div>
}

getter

This is a function that receives the value of an atom. Does not require use in functional components.

import { getter, useAtom } from "@minsize/state"

const COUNT = atom({ default: 0 })

const App = () => {
  const [state, setState] = useAtom(COUNT)
  const handleClick = () => {
    const count = getter(COUNT)
    console.log(count)
  }
  return <div onClick={handleClick}>{state}</div>
}

globalSignal

This API is similar to the SolidJS createStore hook except it takes a Global State state instead of a default value as an argument. It returns a tuple of the current value of the state and a setter function. The setter function may either take a new value as an argument or an updater function which receives the previous value as a parameter.

import { useAtom } from "@minsize/state";

const EXAMPLE_ATOM = atom({ default: "" });

const App = () => {
  const [state, setState] = globalSignal(EXAMPLE_ATOM);
  return <div>{state}</div>;
};

Caching

Atoms can be cached by providing an options object to useAtom, setter and getter. This allows you to manage multiple instances of the same atom with different configurations.

import { atom, useAtom } from "@minsize/state"

const USER = atom<{ name: string }, { userId: number }>({
  default: { name: "NAME" }, // default value
  onRequested: async (options, key) => {
    console.log(options.userId, key)

    const data = await getUser()

    setter([USER, key], "name", data.name)
    // or
    setter([USER, key], data)
  },
  onUpdate: ({ prev, next }, key) => {
    console.log({ prev, next }, key)
  },
})

// Using useAtom with caching
const App = () => {
  const [state, setState] = useAtom(USER, { userId: 1 }, { key: "userId_1" })

  return <div>{state.user.first_name}</div>
}