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

@elyxndra/ui

v0.1.0

Published

Elyxndra's shared chat/agent panel: React + Tailwind v4 components (transcript, tool rows, diffs, approvals, composer with mode/model pickers) styled with VS Code theme variables. Used by Elyxndra's desktop chat app and editor extension.

Downloads

85

Readme

@elyxndra/ui

Elyxndra's agent panel as a React component library: an IDE-style transcript (user turns, streamed replies with collapsible thinking, compact tool rows with expandable output, diff chips with revert, approval and question cards, task list), the composer (mode and model pickers, @ file context, / commands, context meter, stop/send) and the markdown renderer. React 19 + Tailwind v4 + Radix + lucide, styled entirely with the editor's --vscode-* theme variables so it matches whatever theme the host runs. Used by Elyxndra's desktop chat app and editor extension.

npm install @elyxndra/ui react react-dom

Usage

Mount the whole panel and connect it to your host through the bridge (the extension wires it to acquireVsCodeApi(), the desktop app to IPC):

import { createRoot } from "react-dom/client";
import { App, configureBridge } from "@elyxndra/ui";
import "@elyxndra/ui/styles.css"; // Tailwind source — process it with your own Tailwind build

configureBridge({
  post: (m) => host.send(m), // ToExtension messages: send, stop, setMode, openFile, showDiff…
  onMessage: (h) => host.subscribe(h), // ToWebview messages: state, delta, files, focus…
  getState: (key, fallback) => persisted[key] ?? fallback,
  setState: (key, value) => (persisted[key] = value),
});
createRoot(document.getElementById("root")!).render(<App />);

The wire protocol lives in @elyxndra/ui/protocol (ViewState, ToWebview, ToExtension). The host pushes a state snapshot on structural change and delta events while a reply streams; the panel applies deltas locally.

Or compose the pieces yourself:

import { Markdown, AssistantMessage, UserMessage, ToolRow, Composer } from "@elyxndra/ui";
import { useStickToBottom, useAutoGrowTextarea, isSubmitKey, isStopKey } from "@elyxndra/ui";

ViewState.engine carries the daemon's engine view (EngineStateDTO, active engine, model being loaded, typed from @elyxndra/engine/api); engineStateLabel(engine) collapses it to the 4-state label the panel renders. Tool rows take their icon from each tool's definition (ViewState.tools[].def.icon, a lucide name); ToolIcon({ icon }) renders it.

Notes

  • react / react-dom are peer dependencies (one React runtime in the webview); tailwindcss is an optional peer for processing styles.css.
  • @elyxndra/agent (types, parseArguments, attachment helpers, shortModel, contextMeter) and @elyxndra/engine/api (compactNumber, DTO types) are runtime dependencies, imported from their browser-safe entries only.
  • styles.css is Tailwind source (@import "tailwindcss" + tokens mapped to VS Code variables); the consumer's Tailwind build scans this package's dist/ via its @source.
  • The panel renders markdown without raw HTML and never emits a remote image: ![](https://…) in model output is shown as its alt text, not fetched (model output is untrusted, and an image load would be a silent exfiltration channel that skips every approval). Hosts should still set img-src 'self' data: in their CSP. Links open through the host (openExternal / openFile).

Part of the Elyxndra monorepo · MIT