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

eve-devtools

v0.0.3

Published

In-app devtools for eve agents: a live trace panel for turns, reasoning, tool calls, and token usage.

Readme

eve-devtools

An open-source, in-app inspector for eve agents. It turns an agent's event stream into a live visual trace of conversations, reasoning, tool calls, token usage, and timing.

The inspector runs as a floating panel inside your app, making it easier to understand agent behavior without switching to a separate dashboard.

Features

  • Inspect turns, reasoning, tool inputs and outputs, errors, and usage as they happen.
  • Drop it into any browser app with a small framework-agnostic API or the React provider.
  • Keep application styles isolated with a shadow root.
  • Debug locally without sending data anywhere. The package makes no network requests.

Install

bun add eve-devtools

Use

mount() appends the panel to document.body and returns a handle. Pass its onEvent to eve's observe-only callback, and the panel traces the conversation:

import { mount } from "eve-devtools";

const devtools = mount();
const agent = useEveAgent({ onEvent: devtools.onEvent });

onEvent(event) feeds one stream event; unknown events are ignored, so any HandleMessageStreamEvent can be passed through unfiltered. Call devtools.unmount() to remove the panel.

React

Wrap the app once in EveDevtoolsProvider. enabled limits the panel to development builds (React is an optional peer dependency, only needed for this entry):

import { EveDevtoolsProvider } from "eve-devtools/react";

function Root() {
  return (
    <EveDevtoolsProvider enabled={process.env.NODE_ENV === "development"}>
      <App />
    </EveDevtoolsProvider>
  );
}

Anywhere below the provider, read the handle with useEveDevtools() and pass its onEvent to the agent. The handle is undefined until the provider has mounted, so guard the call:

import { useEveDevtools } from "eve-devtools/react";

function Chat() {
  const devtools = useEveDevtools();
  const agent = useEveAgent({ onEvent: devtools?.onEvent });

  return <Conversation agent={agent} />;
}

Contributing

Issues and pull requests are welcome. To run the project locally:

bun install
bun run dev    # demo page with a minimal eve agent traced live
bun run check  # lint, format, and types

The demo lives in demo/ and calls its model through the Vercel AI Gateway. Set AI_GATEWAY_API_KEY in demo/.env.local before starting it.

License

MIT