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

@engenty/wizards

v0.11.0

Published

What your code imports from engenty wizards: plugins at /plugin, wizards in OpenUI chats at /openui.

Readme

@engenty/wizards

What code outside engenty wizards imports, one subpath per use. The runtime and the studio of engenty wizards are not in it.

| Import | What it is | Docs | |---|---|---| | @engenty/wizards/plugin | A plugin's server half: definePlugin and its types | docs/content/dev/plugins | | @engenty/wizards/plugin/studio | A plugin's studio half: defineStudioPlugin | docs/content/dev/plugins/studio.md | | @engenty/wizards/plugin/thread | A messenger channel: ThreadDoor | docs/content/dev/plugins/runners.md | | @engenty/wizards/openui | Wizards in OpenUI chats: the Wizard component | docs/content/dev/integration/openui.md | | @engenty/wizards/openui/server | Its server half: the rules and the list of wizards for the chat's prompt | | | @engenty/wizards/openui/styles.css | The styles the Wizard component draws with | |

Wizards in OpenUI chats

The chat's model decides that a wizard runs and what it already knows. The wizard then runs inside the conversation as its author defined it, drawn by the runner (packages/runner) in the chat's own page.

// The browser
import "@engenty/wizards/openui/styles.css";
import { addWizard, configureWizards, Wizard } from "@engenty/wizards/openui";
import { openuiChatLibrary } from "@openuidev/react-ui/genui-lib";

configureWizards({ runtime: "/wizards-runtime" }); // where the runtime answers
const library = addWizard(openuiChatLibrary, Wizard);
// The server that builds the system prompt
import { addWizard, loadWizards, wizardRules } from "@engenty/wizards/openui/server";

const wizards = await loadWizards("http://localhost:24368", ["<token>"]);
const prompt = addWizard(openuiChatLibrary).prompt({
  ...openuiChatPromptOptions,
  additionalRules: [...(openuiChatPromptOptions.additionalRules ?? []), ...wizardRules(wizards)],
});

What the model writes: Wizard("<token>", "<note>", {plate: "W-12345"}). The prefill starts the page's fields, and the person still sees and sends each page. When the run is done, the component sends a continue_conversation action with the result's texts as its context, and the chat goes on with it. A chat to try it with: examples/openui-chat.

The package

Every release publishes it to npm (scripts/npm-package.mjs, .github/workflows/release.yml). pnpm --filter @engenty/wizards build writes dist/ as it ships (scripts/build.mjs): /openui with the runner and the shared modules it uses bundled in, their types inlined, and the runner's runner.css as styles.css; every other package stays an import, the libraries as dependencies, React, OpenUI, zod and drizzle as peers. Inside this repo everything imports the sources.

Licences

FSL-1.1-MIT, like the repository. dist/openui bundles the runner (packages/runner), which is MIT: its licence ships beside it as dist/openui/LICENSE-MIT.