Skip to main content
JUMP TO:Quick StartCLI CommandsConfigurationPlaywright APIMCP ServerGitHub Actions
Integrations / Storybook(25 of 37)

Storybook

SOURCE AVAILABLE. The CLI includes Storybook index discovery and play-function-aware capture, but the public integration journey has not been externally acceptance-tested.

Point Frontguard at a running Storybook 7 or 8 server to automatically discover stories from /index.json and render each story iframe across your configured viewports.

Playwright and Storybook Visual Workflow
FIG 01 · @FRONTGUARD/PLAYWRIGHT & STORYBOOK — COMPONENT-SCOPED CAPTURE, SPATIAL CLUSTERS & MULTI-VIEWPORT DIFFING

Implemented source

When storybook.url is configured in frontguard.config.ts, Frontguard fetches /index.json (or legacy /stories.json), constructs isolated iframe URLs (/iframe.html?id=<storyId>&viewMode=story), and renders each story through the standard Playwright worker pool.

Configuration

frontguard.config.ts
export default {
  version: 1,
  baseUrl: 'http://localhost:3000',
  storybook: {
    url: 'http://localhost:6006',
    stories: ['components-button--*', 'marketing-pricing--*'],
    exclude: ['*--loading-skeleton'],
  },
  viewports: [375, 1440],
  waitForStability: true,
}

Filtering & play functions

PropertyTypeDefaultDescription
storybook.urlstringRequiredBase URL of your running Storybook instance (e.g., http://localhost:6006).
storybook.storiesstring[]undefinedOptional glob patterns matching story IDs or titles to include.
storybook.excludestring[]undefinedOptional glob patterns of noisy or animated stories to skip.

Play-function handling is built into story capture; there is no waitForPlayFunction configuration switch.

Release limit

Run Storybook yourself, review discovered stories, and use the normal explicit CLI baseline workflow. Do not assume a hosted Storybook review service is included.