Configure Storybook

Storybook is configured via a folder called .storybook, which contains various configuration files.

Configure your Storybook project

Storybook's main configuration (i.e., the main.js|ts) defines your Storybook project's behavior, including the location of your stories, the addons you use, feature flags and other project-specific settings. This file should be in the .storybook folder in your project's root directory. You can author this file in either JavaScript or TypeScript. Listed below are the available options and examples of how to use them.

| Configuration element | Description | | --------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | stories | The array of globs that indicates the location of your story files, relative to main.js | | staticDirs | Sets a list of directories of static files to be loaded by Storybook
staticDirs: ['../public'] | | addons | Sets the list of addons loaded by Storybook
addons: ['@storybook/addon-essentials'] | | typescript | Configures how Storybook handles TypeScript files
typescript: { check: false, checkOptions: {} } | | framework | Configures Storybook based on a set of framework-specific settings
framework: { name: '@storybook/svelte-vite', options:{} } | | core | Configures Storybook's internal features
core: { disableTelemetry: true, } | | docs | Configures Storybook's auto-generated documentation
docs: { autodocs: 'tag' } | | features | Enables Storybook's additional features
See table below for a list of available features | | refs | Configures Storybook composition
refs:{ example: { title: 'ExampleStorybook', url:'https://your-url.com' } } | | logLevel | Configures Storybook's logs in the browser terminal. Useful for debugging
logLevel: 'debug' | | webpackFinal | Customize Storybook's Webpack setup
webpackFinal: async (config:any) => { return config; } | | viteFinal | Customize Storybook's Vite setup when using the vite builder
viteFinal: async (config: Vite.InlineConfig, options: Options) => { return config; } | | env | Defines custom Storybook environment variables.
env: (config) => ({...config, EXAMPLE_VAR: 'Example var' }), | | build | Optimizes Storybook's production build for performance by excluding specific features from the bundle. Useful when decreased build times are a priority.
build: { test: {} } |

Configure story loading

By default, Storybook will load stories from your project based on a glob (pattern matching string) in .storybook/main.js|ts that matches all files in your project with extension .stories.*. The intention is for you to colocate a story file along with the component it documents.

•
└── components
    ├── Button.js
    └── Button.stories.js

If you want to use a different naming convention, you can alter the glob using the syntax supported by picomatch.

For example, if you wanted to pull both .md and .js files from the my-project/src/components directory, you could write:

With a configuration object

Additionally, you can customize your Storybook configuration to load your stories based on a configuration object. For example, if you wanted to load your stories from a packages/components directory, you could adjust your stories configuration field into the following:

When Storybook starts, it will look for any file containing the stories extension inside the packages/components directory and generate the titles for your stories.

With a directory

You can also simplify your Storybook configuration and load the stories using a directory. For example, if you want to load all the stories inside a packages/MyStories, you can adjust the configuration as such:

With a custom implementation

You can also adjust your Storybook configuration and implement custom logic to load your stories. For example, suppose you were working on a project that includes a particular pattern that the conventional ways of loading stories could not solve. In that case, you could adjust your configuration as follows:

Known limitations

Because of the way stories are currently indexed in Storybook, loading stories on demand has a couple of minor limitations at the moment:

• CSF formats from version 1 to version 3 are supported.
• Custom storySort functions are allowed based on a restricted API.

Configure story rendering

To control the way stories are rendered and add global decorators and parameters, create a .storybook/preview.js file. This is loaded in the Canvas UI, the “preview” iframe that renders your components in isolation. Use preview.js for global code (such as CSS imports or JavaScript mocks) that applies to all stories.

The preview.js file can be an ES module and export the following keys:

• decorators - an array of global decorators
• parameters - an object of global parameters
• globalTypes - definition of globalTypes

If you’re looking to change how to order your stories, read about sorting stories.

Configure Storybook’s UI

To control the behavior of Storybook’s UI (the “manager”), you can create a .storybook/manager.js file.

This file does not have a specific API but is the place to set UI options and to configure Storybook’s theme.