Skip to content
Branch: master
Find file Copy path
Find file Copy path
4 contributors

Users who have contributed to this file

@thollander @shilman @ndelangen @antony
172 lines (125 sloc) 4.56 KB
id title
Storybook for Svelte

Automatic setup

You may have tried to use our quick start guide to setup your project for Storybook. If it failed because it couldn't detect you're using svelte, you could try forcing it to use svelte:

npx -p @storybook/cli sb init --type svelte

Manual setup

If you want to set up Storybook manually for your Svelte project, this is the guide for you.

It is very important to remember that Svelte components are precompiled from .svelte or .html files to vanilla javascript, so there is no 'runtime'.

Step 1: Add dependencies

Add @storybook/svelte

Add @storybook/svelte to your project. To do that, run:

npm install @storybook/svelte --save-dev

@babel/core, and babel-loader

Make sure that you have @babel/core, and babel-loader in your dependencies as well because we list these as a peer dependencies:

npm install babel-loader @babel/core --save-dev 

Step 2: Add a npm script

Then add the following NPM script to your package.json in order to start the storybook later in this guide:

  "scripts": {
    "storybook": "start-storybook"

Step 3: Create the config file

For a basic Storybook configuration, the only thing you need to do is tell Storybook where to find stories.

To do that, create a file at .storybook/config.js with the following content:

import { configure } from '@storybook/svelte';

function loadStories() {
  // You can require as many stories as you need.

configure(loadStories, module);

That'll load stories in ../stories/index.js. You can choose where to place stories, you can co-locate them with source files, or place them in an other directory.

Requiring all your stories becomes bothersome real quick, so you can use this to load all stories matching a glob.

import { configure } from '@storybook/svelte';

function loadStories() {
  const req = require.context('../stories', true, /\.stories\.js$/);
  req.keys().forEach(filename => req(filename));

configure(loadStories, module);

Step 4: Write your stories

Now create a ../stories/index.js file, and write your first story like this:

import { storiesOf } from '@storybook/svelte';
import MyButton from '../components/MyButton.svelte';

storiesOf('MyButton', module)
  .add('with text', () => ({
    Component: MyButton,
    props: {
      buttonText: 'some text',
  .add('with some emojies', () => ({
    Component: MyButton,

    props: {
      buttonText: '😀 😎 👍 💯',

Svelte storybooks don't support using templates in a story yet. Instead, you can create a .svelte file to compose components together, or simply to access all normal Svelte functionality, like slots.

So you can create a story "view" file, essentially just a .svelte file to load your components into to test.

<!-- MyButtonView  -->
<MyButton {rounded} on:click>

In this example, the on:click that is heard on the MyButton component is simply passed up to the containing component MyButtonView using the svelte shorthand. It's the equivalent to on:click="fire('click', event)", but it's worth knowing about especially in this "component wrapper" scenario.

If your component doesn't use slots, you don't need to do this, but if it does or some other svelte functionality that requires the component to exist in a svelte view, then this is how to do that.

You would then write a story for this "view" the exact same way you did with a component.

import { storiesOf } from '@storybook/svelte';
import MyButtonView from '../views/MyButtonView.svelte';

storiesOf('Button', module)
  .add('wrapped component(s) example', () => ({
    Components: MyButtonView,

    props: {
      buttonText: 'some text',
      rounded: true,

    on: {
      click: (event) => {
        console.log('clicked', event);

Each story is a single state of your component. In the above case, there are two stories for the demo button component:

  ├── with text
  ├── with emoji
  └── wrapped component(s) example

Finally: Run your Storybook

Now everything is ready. Run your storybook with:

npm run storybook

Storybook should start, on a random open port in dev-mode.

Now you can develop your components and write stories and see the changes in Storybook immediately since it uses Webpack's hot module reloading.

You can’t perform that action at this time.