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

@cristaline/react

v1.0.0

Published

React.js bridge for cristaline.

Readme

@cristaline/react

React.js bridge for @cristaline/core

Requirements

Usage

npm create vite -- --template react-ts project
cd project
npm install @cristaline/core @cristaline/react zod

[!WARNING] It is highly recommended to use a parsing library like Zod in order to ease the creation of robust and resilient schemas, but you can use any library of your choice.

touch src/event-store.ts
import type { EventShape } from "@cristaline/core";
import type { ZodSchema } from "zod";

import { defineEventStore } from "@cristaline/react"
import { MemoryEvent, MemoryState } from "@cristaline/core";
import { z } from "zod"

const eventSchema = z.object({
  type: z.literal("TodoAdded"),
  version: z.literal(1),
  identifier: z.string(),
  date: z.date({ coerce: true }),
  data: z.object({
    id: z.string(),
    title: z.string()
  })
}) satisfies ZodSchema<EventShape>;

type Event = z.infer<typeof eventSchema>

type Todo = {
  id: string,
  title: string
}

type State = {
  todos: Todo[]
}

export const { EventStoreProvider, useEventStore } = defineEventStore<State, Event>({
  event: MemoryEvent.for({
    events: [],
    parser: eventSchema.parse
  }),
  state: MemoryState.for({
    state: {
      todos: []
    }
  }),
  replay: (state, event) => {
    switch (event.type) {
      case "TodoAdded":
        return {
          ...state,
          todos: [
            ...state.todos,
            event.data
          ]
        }
    }
  }
});
touch src/main.tsx
import { createRoot } from 'react-dom/client'
import App from './App.tsx'
import { EventStoreProvider } from './eventstore'

createRoot(document.getElementById('root')!).render(
  <EventStoreProvider>
    <App />
  </EventStoreProvider>
)
touch src/App.tsx
import { useEventStore } from "./event-store";

export default function App() {
  const eventStore = useEventStore();

  return null;
}

Changelogs

Versions

1.0.0

Major changes

  • Renamed the eventAdapter property from the arguments of the defineEventStore function to event
  • Renamed the stateAdapter property from the arguments of the defineEventStore function to state

Minor changes

None.

Bug & security fixes

None.

0.1.0

Major changes

None.

Minor changes

None.

Bug & security fixes

None.

License

See LICENSE.