Back to Storybook

Addon API

docs/addons/addons-api.mdx

10.3.612.6 KB
Original Source

Storybook's API allows developers to interact programmatically with Storybook. With the API, developers can build and deploy custom addons and other tools that enhance Storybook's functionality.

Core Addon API

Our API is exposed via two distinct packages, each one with a different purpose:

  • storybook/manager-api used to interact with the Storybook manager UI or access the Storybook API.
  • storybook/preview-api used to control and configure the addon's behavior.
<CodeSnippets path="storybook-addons-api-imports.md" />

addons.add()

The add method allows you to register the type of UI component associated with the addon (e.g., panels, toolbars, tabs). For a minimum viable Storybook addon, you should provide the following arguments:

  • type: The type of UI component to register.
  • title: The title to feature in the Addon Panel.
  • render: The function that renders the addon's UI component.
<CodeSnippets path="storybook-addon-panel-initial.md" /> <Callout variant="info"> The render function is called with `active`. The `active` value will be true when the panel is focused on the UI. </Callout>

addons.register()

Serves as the entry point for all addons. It allows you to register an addon and access the Storybook API. For example:

<CodeSnippets path="storybook-addons-api-register.md" />

Now you'll get an instance to our StorybookAPI. See the api docs for Storybook API regarding using that.

addons.getChannel()

Get an instance to the channel to communicate with the manager and the preview. You can find this in both the addon register code and your addon’s wrapper component (where used inside a story).

It has a NodeJS EventEmitter compatible API. So, you can use it to emit events and listen to events.

<CodeSnippets path="storybook-addons-api-getchannel.md" />

makeDecorator

Use the makeDecorator API to create decorators in the style of the official addons. Like so:

<CodeSnippets path="storybook-addons-api-makedecorator.md" /> <Callout variant="info"> If the story's parameters include `{ exampleParameter: { disable: true } }` (where `exampleParameter` is the `parameterName` of your addon), your decorator will not be called. </Callout>

The makeDecorator API requires the following arguments:

  • name: Unique name to identify the custom addon decorator.
  • parameterName: Sets a unique parameter to be consumed by the addon.
  • skipIfNoParametersOrOptions: (Optional) Doesn't run the decorator if the user hasn't options either via decorators or parameters.
  • wrapper: your decorator function. Takes the getStory, context, and both the options and parameters (as defined in skipIfNoParametersOrOptions above).

Storybook API

Storybook's API allows you to access different functionalities of Storybook UI.

api.selectStory()

The selectStory API method allows you to select a single story. It accepts the following two parameters; story kind name and an optional story name. For example:

<CodeSnippets path="button-story-with-addon-example.md" />

This is how you can select the above story:

<CodeSnippets path="storybook-addons-api-selectstory.md" />

api.selectInCurrentKind()

Similar to the selectStory API method, but it only accepts the story as the only parameter.

<CodeSnippets path="storybook-addons-api-selectincurrentkind.md" />

api.setQueryParams()

This method allows you to set query string parameters. You can use that as temporary storage for addons. Here's how you define query params:

<CodeSnippets path="storybook-addons-api-setqueryparams.md" />

Additionally, if you need to remove a query parameter, set it as null instead of removing them from the addon. For example:

<CodeSnippets path="storybook-addons-api-disablequeryparams.md" />

api.getQueryParam()

Allows retrieval of a query parameter enabled via the setQueryParams API method. For example:

<CodeSnippets path="storybook-addons-api-getqueryparam.md" />

api.getUrlState(overrideParams)

This method allows you to get the application URL state, including any overridden or custom parameter values. For example:

<CodeSnippets path="storybook-addons-api-geturlstate.md" />

api.getStoryHrefs(storyId, options?)

Get the manager and preview URLs for a story. URLs are relative to the current Storybook, unless base is set, or in case of previewHref with refId set.

  • storyId (required): The ID of the story to get the URLs for
  • options (optional):
    • base: Return an absolute href based on the current origin or network address.
    • inheritArgs: Inherit args from the current URL. If storyId matches current story, inheritArgs defaults to true.
    • inheritGlobals: Inherit globals from the current URL. Defaults to true.
    • queryParams: Additional query params to append to the URL (args and globals are merged when inheriting).
    • refId: ID of the ref to get the URL for (for composed Storybooks)
    • viewMode: The view mode to use, defaults to 'story'.
<CodeSnippets path="storybook-addons-api-getstoryhrefs.md" />

api.on(eventName, fn)

This method allows you to register a handler function called whenever the user navigates between stories.

<CodeSnippets path="storybook-addons-api-on.md" />

api.openInEditor(payload)

Opens a file in the configured code editor. Useful for "Edit in IDE" functionality in addons.

  • payload.file: The file path to open (required)
  • payload.line: Optional line number to jump to
  • payload.column: Optional column number to jump to

Returns a Promise that resolves with information about whether the operation was successful.

<CodeSnippets path="storybook-addons-api-openineditor.md" />

api.getCurrentStoryData()

Returns the current story's data, including its ID, kind, name, and parameters.

<CodeSnippets path="storybook-addons-api-getcurrentstorydata.md" />

api.toggleFullscreen(toggled?)

Toggles the fullscreen mode of the Storybook UI. Pass true to enable fullscreen, false to disable, or omit to toggle the current state.

<CodeSnippets path="storybook-addons-api-togglefullscreen.md" />

api.togglePanel(toggled?)

Toggles the visibility of the addon panel. Pass true to show the panel, false to hide, or omit to toggle the current state.

<CodeSnippets path="storybook-addons-api-togglepanel.md" />

api.addNotification(notification)

Displays a notification in the Storybook UI. The notification object should contain id, content, and optionally duration and icon.

<CodeSnippets path="storybook-addons-api-addnotification.md" />

addons.setConfig(config)

This method allows you to override the default Storybook UI configuration (e.g., set up a theme or hide UI elements):

<CodeSnippets path="storybook-config-layout.md" />

The following table details how to use the API values:

NameTypeDescriptionExample Value
navSizeNumber (pixels)The size of the sidebar that shows a list of stories300
bottomPanelHeightNumber (pixels)The size of the addon panel when in the bottom position200
rightPanelWidthNumber (pixels)The size of the addon panel when in the right position200
panelPositionStringWhere to show the addon panel'bottom' or 'right'
enableShortcutsBooleanEnable/disable shortcutstrue
showToolbarBooleanShow/hide toolbartrue
themeObjectStorybook Theme, see next sectionundefined
selectedPanelStringId to select an addon panelstorybook/actions/panel
initialActiveStringSelect the default active tab on Mobilesidebar or canvas or addons
sidebarObjectSidebar options, see below{ showRoots: false }
toolbarObjectModify the tools in the toolbar using the addon id{ fullscreen: { hidden: false } }

The following options are configurable under the sidebar namespace:

NameTypeDescriptionExample Value
showRootsBooleanDisplay the top-level nodes as a "root" in the sidebarfalse
collapsedRootsArraySet of root node IDs to visually collapse by default['misc', 'other']
renderLabelFunctionCreate a custom label for tree nodes; must return a ReactNode(item, api) => <abbr title="...">{item.name}</abbr>

The following options are configurable under the toolbar namespace:

NameTypeDescriptionExample Value
[id]StringToggle visibility for a specific toolbar item (e.g. title, zoom){ hidden: false }

Storybook hooks

To help streamline addon development and reduce boilerplate code, the API exposes a set of hooks to access Storybook's internals. These hooks are an extension of the storybook/manager-api module.

useStorybookState

It allows access to Storybook's internal state. Similar to the useglobals hook, we recommend optimizing your addon to rely on React.memo, or the following hooks; useMemo, useCallback to prevent a high volume of re-render cycles.

<CodeSnippets path="storybook-addons-api-usestorybookstate.md" />

useStorybookApi

The useStorybookApi hook is a convenient helper to allow you full access to the Storybook API methods.

<CodeSnippets path="storybook-addons-api-useapi.md" />

useChannel

Allows setting subscriptions to events and getting the emitter to emit custom events to the channel.

The messages can be listened to on both the iframe and the manager.

<CodeSnippets path="storybook-addons-api-usechannel.md" />

useAddonState

The useAddonState is a useful hook for addons that require data persistence, either due to Storybook's UI lifecycle or for more complex addons involving multiple types (e.g., toolbars, panels).

<CodeSnippets path="storybook-addons-api-useaddonstate.md" />

useParameter

The useParameter retrieves the current story's parameters. If the parameter's value is not defined, it will automatically default to the second value defined.

<CodeSnippets path="storybook-addons-api-useparameter.md" />

useGlobals

Extremely useful hook for addons that rely on Storybook Globals. It allows you to obtain and update global values. We also recommend optimizing your addon to rely on React.memo, or the following hooks; useMemo, useCallback to prevent a high volume of re-render cycles.

<CodeSnippets path="storybook-addons-api-useglobal.md" />

useArgs

Hook that allows you to retrieve or update a story's args.

<CodeSnippets path="args-usage-with-addons.md" />

Learn more about the Storybook addon ecosystem