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

@anvia/react

v0.8.10

Published

React hooks and client transports for Anvia applications.

Readme

@anvia/react

React hooks and client transports for Anvia applications.

import { useChat } from "@anvia/react";
import { useState } from "react";

export function Chat() {
  const chat = useChat({ endpoint: "/api/chat" });
  const [input, setInput] = useState("");

  return (
    <form
      onSubmit={(event) => {
        event.preventDefault();
        void chat.sendMessage(input);
        setInput("");
      }}
    >
      <div>
        {chat.messages.map((message) => (
          <p key={message.id}>
            {message.parts
              .filter((part) => part.type === "text")
              .map((part) => part.text)
              .join("")}
          </p>
        ))}
      </div>
      <input value={input} onChange={(event) => setInput(event.target.value)} />
      <button disabled={chat.status === "streaming"}>Send</button>
    </form>
  );
}

Exports

  • readJsonlStream(stream) parses newline-delimited JSON streams.
  • readSseStream(stream) parses Server-Sent Events with JSON data: payloads.
  • fetchEventStream(url, options) fetches JSONL or SSE streams as AsyncIterable.
  • createFetchTransport(options) creates an EventTransport; it defaults to POST JSON and omits implicit bodies for GET/HEAD.
  • createChatTransport(options) creates the default fetch-backed chat transport.
  • useChat(options) manages UIMessage[] chat state from any EventTransport, including optional human-input approval/question state and opt-in stream resume.
  • useCompletion(options) appends completion turns into UIMessage[] state and exposes derived completion text.
  • useSmoothStreamText(content, options) smooths an append-only string for display without changing stream events or message state.

Default hook requests use one shared wire shape:

type UIStreamRequest = {
  messages: Message[];
  stream: true;
  metadata?: JsonValue;
};

Hooks convert their local UIMessage[] state into core messages before sending. Custom createRequest callbacks receive { messages, uiMessages, coreMessages }, where messages and uiMessages are UI-shaped for compatibility and coreMessages is the default wire payload.

The shared boundary is:

type EventTransport<TRequest, TEvent> = {
  send(request: TRequest, options?: TransportOptions): AsyncIterable<TEvent>;
};

Default hooks can consume raw createCompletionStream(...) events, raw agent stream events, or UIStreamEvent records. A completion endpoint can return:

createEventStream(createCompletionStream(model, { messages: body.messages }));

For chat streams that should survive navigation or reload, pair useChat({ resume: { key } }) with an endpoint that returns createEventStream(events, { resumable: { id, store } }) and handles resume bodies containing { resume: { streamId, after } }.