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

@studio-vaai/react-headless

v0.1.3

Published

React hooks for the studio vaai virtual try-on flow (layer 2)

Readme

@studio-vaai/react-headless

React hooks and a provider for the studio vaai virtual try-on flow — the headless layer: all behaviour, no UI.

Want prebuilt, styled UI instead? Use @studio-vaai/react-components.

Install

npm install @studio-vaai/react-headless @studio-vaai/js-client

Peer dependencies: react and react-dom (^18 or ^19).

Import this package only in application code — its lower layers stay transitive. Two optional subpath entrypoints re-export them if you need direct access (no React in either):

  • @studio-vaai/react-headless/client — the HTTP contract and createClient stub.
  • @studio-vaai/react-headless/machine — the XState machines.

Quick start

  1. Obtain a StudioVaaiClient (e.g. createFetchStudioVaaiClient from @studio-vaai/js-client).
  2. Wrap your tree with StudioVaaiProvider, passing client and input.
  3. In children, call useStudioVaaiActor().
"use client";

import {
  StudioVaaiProvider,
  useStudioVaaiActor,
  type DefaultRootInput,
  type StudioVaaiClient,
} from "@studio-vaai/react-headless";

function App({ client }: { client: StudioVaaiClient }) {
  const input: Omit<DefaultRootInput, "client"> = {
    productId: "...",
    selection: { variantSlug: "", attributes: {} },
  };

  return (
    <StudioVaaiProvider client={client} input={input}>
      <Step />
    </StudioVaaiProvider>
  );
}

function Step() {
  const { state, dispatch } = useStudioVaaiActor();
  return <pre>{JSON.stringify(state.value, null, 2)}</pre>;
}

useStudioVaaiActor() returns:

| Field | Role | | -------------- | ------------------------------------------------------------------------ | | state | Current snapshot of the flow — which step you're on, plus context data. | | dispatch | Send a typed event (e.g. { type: "…" }) to advance or branch the flow. | | actor | The underlying actor, for advanced use and debugging. |

Use useStudioVaaiSelector when you only need a slice of state, to limit re-renders.

Custom root machine

createStudioVaaiContext(yourMachine) returns a StudioVaaiProvider and hooks typed for your own machine. The default export is built on defaultRootMachine, which is also re-exported for composition.

Errors

| Error | When | | ----------------------------------------- | ------------------------------------------------------------------------ | | StudioVaaiProviderError | A hook is used outside StudioVaaiProvider. | | StudioVaaiClientNotImplementedError | createClient() was called without a transport. | | ApiFailureError | An actor threw after a failed API result; failure holds the API error. |

Next.js / SSR

Mount the provider and hooks under a "use client" boundary. This library does not assume window in its module scope.

License

MIT