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

@generative-dom/vue

v0.1.0

Published

Official Vue 3 wrapper for Generative DOM streaming markdown renderer

Readme

@generative-dom/vue

Official Vue 3 wrapper for the Generative DOM streaming markdown renderer.

A thin (~150 LOC) layer over @generative-dom/core that handles the Vue lifecycle for you. Two public APIs:

  • <GenerativeDomRenderer> — declarative component for the common "render this markdown string" case.
  • useGenerativeDom() — imperative composable for streaming sources (LLM SDKs, server-sent events, etc.).

Vue is a peer dependency. The wrapper supports Vue 3.3+.

Installation

pnpm add @generative-dom/vue @generative-dom/core
# plus whatever plugins you want, e.g.:
pnpm add @generative-dom/plugin-markdown-base @generative-dom/plugin-markdown-heading

Component usage

<script setup lang="ts">
import { GenerativeDomRenderer } from '@generative-dom/vue';
import { markdownBase } from '@generative-dom/plugin-markdown-base';
import { markdownHeading } from '@generative-dom/plugin-markdown-heading';

const plugins = [markdownBase(), markdownHeading()];

defineProps<{ text: string }>();
</script>

<template>
  <GenerativeDomRenderer
    :markdown="text"
    :plugins="plugins"
    class="prose"
  />
</template>

When markdown changes the component calls reset() then push() then flush() on the underlying instance, so the container always reflects the latest string. When plugins or debounceMs changes the Generative DOM instance is destroyed and re-created. On unmount destroy() is called.

Props

| Prop | Type | Notes | | ---- | ---- | ----- | | plugins | GenerativeDomPlugin[] | Required. | | markdown | string | Optional. Triggers reset + push + flush when it changes. | | debounceMs | number | Default 16 (~1 frame). | | onError | (error) => void | Forwarded to Generative DOM's onError. |

Standard class / style attrs pass through to the container <div>.

Events

| Event | Payload | Notes | | ----- | ------- | ----- | | event | (name: string, data: unknown) | Receives plugin events (button-click, link-click, heading-rendered, token, events:progress, interactive:state). |

<GenerativeDomRenderer :markdown="text" :plugins="plugins" @event="onEvent" />

Composable usage (streaming)

<script setup lang="ts">
import { onMounted } from 'vue';
import { useGenerativeDom } from '@generative-dom/vue';
import { markdownBase } from '@generative-dom/plugin-markdown-base';
import { markdownHeading } from '@generative-dom/plugin-markdown-heading';

const props = defineProps<{ stream: AsyncIterable<string> }>();

const { containerRef, push, flush, reset } = useGenerativeDom({
  plugins: [markdownBase(), markdownHeading()],
});

onMounted(async () => {
  reset();
  for await (const chunk of props.stream) push(chunk);
  flush();
});
</script>

<template>
  <div ref="containerRef" class="prose" />
</template>

The composable returns:

{
  containerRef: Ref<HTMLElement | null>; // attach to your container element
  push:  (chunk: string) => void;
  flush: () => void;
  reset: () => void;
  on:    (event: string, handler) => void;
  off:   (event: string, handler) => void;
}

Why a wrapper?

@generative-dom/core is framework-agnostic and does not depend on Vue. The wrapper exists so Vue users don't have to write the onMounted / onBeforeUnmount / watch plumbing themselves — it is the same code you would write, just maintained centrally.

License

MIT