Coming from Storybook

Poveste is a component playground built on Vite, for Vue, Nuxt, Svelte, SvelteKit and Quasar. If you already run Storybook, this page is what is different here — not a case for switching.

A story is a component, not a separate format

There is no story format to learn. A story is a file in the framework you already write, using two components:

<!-- src/components/Button.story.vue -->
<script setup>
import Button from './Button.vue'
</script>

<template>
  <Story title="Button">
    <Variant title="Primary">
      <Button primary>
        Save
      </Button>
    </Variant>
    <Variant title="Disabled">
      <Button disabled>
        Save
      </Button>
    </Variant>
  </Story>
</template>

That is the whole API for a basic story: <Story> and <Variant>. State and controls are added with initState and the Hst* controls when a variant needs them, and Poveste builds a control per declared prop on its own — for Vue from the rendered component, for Svelte from the component's source.

Your Vite config is the build

Poveste resolves your Vite config and runs the book through it, so aliases, plugins, define and your TypeScript and CSS setup apply to stories because they are the same pipeline — not because they were copied into a second one. Where a framework needs handling, its plugin does it: @poveste/plugin-quasar fetches the config Quasar builds asynchronously, @poveste/plugin-nuxt runs a Nuxt build, and you configure neither by hand.

Poveste can also be configured entirely from vite.config.ts under a poveste key, with no config file of its own — which is how examples/svelte and examples/sveltekit are set up.

What a book weighs

examples/vue, same story:build command either side of #590:

	highlighter chunk	whole book
before	9,960 KB	14,012 KB
after	1,346 KB	4,992 KB

The highlighter had been importing from the shiki barrel, which ships every grammar and theme; it now names the two the source pane uses. pnpm test:bundle-size holds a built book to a 6,500 KB ceiling and each chunk to its own, so this stays true rather than being a number from one afternoon.

Five frameworks, each with a book CI builds

Vue, Nuxt, Svelte, SvelteKit and Quasar each have an example book in this repository, built and driven by Playwright on every commit. The shared specs run against all of them, so support means a job that fails rather than a row in a table.

What Poveste does not do

Worth knowing before you spend an afternoon:

• No React, Angular or Solid. The plugin interface is public and a framework plugin is possible, but nobody has written those. For React, Ladle is Vite-native and does this well.
• No addon ecosystem. Poveste has a plugin API for collection and setup, and official plugins for the frameworks, Tailwind, Percy and screenshots. It is not a marketplace, and an addon you rely on has no equivalent here.
• It is a small project. Poveste is a maintained fork of histoire, currently pre-1.0 — what 1.0 means is written down, along with what a deprecation promises.

Trying it

pnpm i -D poveste @poveste/plugin-vue, a poveste.config.ts with the plugin in it, and poveste dev. The Getting started page has the exact commands per framework, and every framework page has a working example to copy.