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

@4djs/ai-widgets

v0.1.1

Published

Built-in assistant widgets for Data Explorer. Widgets are **render-only**: they receive a data envelope and paint UI. They never fetch from the datastore.

Readme

@4djs/ai-widgets

Built-in assistant widgets for Data Explorer. Widgets are render-only: they receive a data envelope and paint UI. They never fetch from the datastore.

Hosts (e.g. Data Explorer) gather data with @datastore/query, shape an envelope, then call @widgets/render. Results render inline via WidgetRenderer.

Usage

import {
  WidgetRenderer,
  listBuiltinWidgets,
  listWidgetAiGuidance,
  getWidgetRenderPropsFromResult,
  buildWidgetRenderInputSchema,
  buildWidgetRenderToolDescription,
  parseWidgetRenderArgs,
} from "@4djs/ai-widgets";
import "@4djs/ai-widgets/styles.css";

Render a tool result

const props = getWidgetRenderPropsFromResult(step.result);
if (props) {
  return <WidgetRenderer {...props} mode={props.mode ?? "light"} />;
}

Host tool (data in)

Compose the tool description and JSON Schema from the registry so per-widget AI instructions stay next to each component (not in the app system prompt):

const opts = { disabledWidgetTypes };
const schema = buildWidgetRenderInputSchema(opts);
const description = buildWidgetRenderToolDescription(opts);
const parsed = parseWidgetRenderArgs(args, opts);
if (!parsed.ok) return toolResultErr(parsed.error);
return toolResultOk({
  widget: { title: parsed.value.title, data: parsed.value.data },
});

Each widget definition can declare:

{
  type: "pie",
  label: "Pie Chart",
  description: "Part-to-whole slices", // human UI
  example: { type: "pie", values: [{ label: "A", value: 3 }] },
  ai: {
    summary: "Part-to-whole distribution as a pie",
    dataShape: '{ "type": "pie", "values": [{ "label", "value" }] }',
    aliases: 'Also accepts series/data as [{ "key", "value" }]',
  },
  Render: …
}

Example tool args:

{
  "title": "Cars by category",
  "data": {
    "type": "pie",
    "values": [
      { "label": "SUV", "value": 12 },
      { "label": "Sedan", "value": 8 }
    ]
  }
}

Built-in types

KPI, line, area, bar, pie, donut, scatter, heatmap, table, gauge, progress, funnel, map, timeline, filter.

Scripts

bun run typecheck
bun run test
bun run lint

Profile enablement

Data Explorer stores disabledWidgetTypes per profile. The Widgets settings panel toggles types and refreshes the @widgets/render schema so disabled types are omitted from the model tool enum.