Skip to content
한국어
Contact us

Blog

Storybook's 11.0 alpha has shipped five times, and what stands out in the notes is removal, not new features. Here is what a design system team should check.

Published

Korean version of this postView as Markdown

Storybook's next major, 11.0, has reached its fifth alpha this week, from alpha 4 to alpha 8. Read the release notes and what stands out is not a new feature. It is what disappears.

The current stable line, 10.6, shipped three times over the same period: 10.6.2, 10.6.3 and 10.6.4. The changes are small, but they point the same way.

The npm package is downloaded 17,692,795 times a week. With that many teams on it, even a small removal breaks someone's setup.

A stack of component cards with old stickers peeled off

The alpha 5 release notes collect the removals.

  • The storybook ai command is gone
  • The viewport.defaultViewport parameter and the responsiveViewport export are gone
  • The create-new-story button in the sidebar is gone
  • The legacy highlight object format and the changeDetection feature flag are gone

Alpha 8 drops the deprecated parameters.component path for Svelte.

Feature lists rarely show it, but much of the change sits where config files are read and rewritten.

  • In alpha 8, the tool that reads CSF files runs on OXC instead of Babel
  • In the same alpha, Svelte CSF moves to CSF factories (definePreview)
  • Vitest 5 support arrived in alpha 5, and 10.6.3 carries the same fix
  • The upgrade command gets reworked. It installs every project in a pnpm workspace, keeps related scoped packages on one major, migrates CSF2 argTypes and reports an unfinished upgrade as a failure

A small bridge between two islands with a signpost

For a design system team, the 11.0 alpha is not a version to install now. It is a version to read, so you know whether your setup relies on something that is about to go. Three checks are enough.

  • Search .storybook/preview for viewport.defaultViewport
  • Look for team docs that lean on the sidebar's create-new-story button or the storybook ai command
  • Run the upgrade command once on a separate branch and write down how far the automatic migration goes

Staying on the stable line is not urgent either. Older lines keep getting fixes. 9.1.21 and 8.6.19 carry the same security hardening. It limits the messages the preview sends to known manager origins and stops the dev server from being embedded in an iframe from anywhere but localhost.

Still, while the alpha numbers climb this fast, keeping a point you can return to is the team's job.

A rounded shield in front of a closed box

Sources

Keep reading