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

@octanejs/xstate-store

v0.0.15

Published

XState Store for Octane — re-exports the framework-agnostic @xstate/store core unchanged and ports the @xstate/store-react 2.0.0 binding onto Octane hooks.

Readme

@octanejs/xstate-store

XState Store for Octane — a port of @xstate/[email protected].

The @xstate/store core is framework-neutral, so it is reused unmodified and re-exported wholesale from this entry point, exactly as upstream does. Only the React binding is ported. See UPSTREAM.md for the pin, the export crosswalk, and the disposition of every upstream test.

npm install @octanejs/xstate-store
pnpm add @octanejs/xstate-store

Usage

import { createStore, useSelector } from '@octanejs/xstate-store';

const store = createStore({
	context: { count: 0 },
	on: {
		inc: (context, event: { by: number }) => ({
			...context,
			count: context.count + event.by,
		}),
	},
});

export function Counter() @{
	const count = useSelector(store, (s) => s.context.count);

	<button onClick={() => store.trigger.inc({ by: 1 })}>{count as string}</button>
}

createStoreHook bundles the store and its selector into one hook:

import { createStoreHook } from '@octanejs/xstate-store';

const useCountStore = createStoreHook({
	context: { count: 0 },
	on: { inc: (context, event: { by: number }) => ({ ...context, count: context.count + event.by }) },
});

export function Counter() @{
	const [count, store] = useCountStore((s) => s.context.count);

	<button onClick={() => store.trigger.inc({ by: 1 })}>{count as string}</button>
}

Exports

Everything @xstate/[email protected] exports (createStore, createStoreConfig, createStoreLogic, createAtom, createAtomConfig, createAsyncAtom, createReducerAtom, fromStore, shallowEqual, and the full type surface), plus the ported hooks useSelector, useStore, useAtom, useAtomState, and createStoreHook.

Intentional differences from @xstate/store-react on React

  • Conditional hook calls are legal. Upstream calls hooks inside if branches in useSelector and useAtom. On React that only works because the branch is stable for a given call site. Octane keys hooks by compiler-assigned call site rather than call order, so the shape is sound here — and if a call site ever did flip branches, Octane keeps independent hook cells per branch instead of corrupting hook order.
  • useSyncExternalStore skips React's commit-time getSnapshot re-read when the rendered value was unchanged, because Octane's synchronous renderer closes the concurrent-interleaving window React guards there.
  • Server snapshots. getServerSnapshot is optional in Octane and falls back to getSnapshot; React throws when it is missing. Every hook here supplies one.