Running Storybook?

Storybook broken after an upgrade? We ship it properly.

Storybook upgrades between major versions have a reputation for a reason. Addons drop out, Webpack switches to Vite under the hood, args and argTypes get renamed, and the build that worked on Friday is red on Monday. We walk the config, rebuild it against the current major, and leave the component library usable again.

  • Since 2015Fixing technology
  • FreeEstimates
  • US teamReal engineers

storybook.log

still failing

What it is

Storybook at a glance

Storybook is an open-source workshop for building UI components in isolation, originally released by Arunoda Susiripala in 2016 and now maintained under the Storybook project within Chromatic. Each component is written as one or more stories, which Storybook renders in a sandboxed environment with controls to change props, documentation generated from the source, and hooks for accessibility and visual regression tests.

It supports React, Vue, Svelte, Angular, Web Components, Ember, HTML and more through framework presets. Storybook 7 replaced Webpack with a configurable builder that can run on Vite, consolidated addon-essentials, and simplified the args API. Storybook 8 continued that direction, removed deprecated APIs, and tightened the integration with Chromatic for visual testing. The result is a cleaner tool with a real upgrade cost.

Type
UI component workshop and documentation tool
First released
2016
License
MIT, open source
Maintained by
Chromatic and the Storybook contributors
Typically used for
Component libraries, design system documentation, visual regression testing, isolated UI development, accessibility checks

The honest version

Storybook pros and cons

No technology is all upside. This is where Storybook earns its place and where it tends to cause trouble.

Where Storybook is strong

  • Components in isolationBuilding a component outside the app it lives in, with every prop combination visible, catches bugs the app itself would have hidden under noise.
  • Great for design systemsA living catalogue of every component, every variant and every token makes the design system real to engineers who were not in the kickoff meeting.
  • Accessibility addon pays for itselfThe a11y addon flags axe violations on every story, so accessibility shifts from an audit at the end to a signal during normal development.
  • Visual testing fits in naturallyChromatic, Percy and Playwright all understand Storybook, so hooking visual regression tests into CI requires wiring rather than a bespoke build.
  • Supports every major frameworkReact, Vue, Svelte and Angular share one runtime and one developer experience, which matters for teams running more than one front-end stack.
  • Decent documentation storyAutodocs reads prop types or JSDoc and generates reference pages without a second documentation tool.

Where Storybook bites

  • Upgrades between majors are heavy workBuilder changes, renamed APIs, dropped addons and parser updates stack together. A Storybook upgrade on a real codebase is a real week of work, not an afternoon.
  • Addon ecosystem lags the coreEvery release a handful of addons do not yet support the new version, and projects depending on them either wait, fork or do without.
  • Build times climb with the catalogueA large project with hundreds of stories and MDX pages builds slowly, and both the manager and the preview grow heavier over time.
  • Custom Webpack or Vite config gets staleProjects with a bespoke builder config inherited from Storybook 6 find most of it is either rewritten or ignored by the current builder, which turns an upgrade into a rewrite.
  • args and argTypes schema shiftsThe args API has been quietly reshaped across versions, and a story that worked on 6.5 can need surgery on 8 even though the component itself has not changed.
  • React-docgen-typescript is fragileComplex generics, conditional types and re-exported component types regularly fail to parse, producing controls that look empty or wrong without a clear error.

Sound familiar?

Common Storybook problems we fix

The Storybook problems that bring people to us, and what you have once each one is fixed.

Failed to build Storybook

Storybook refuses to build after a major upgrade

Addons left behind, a builder that did not come along cleanly, or a preview.js using an API that was renamed. Each error points at the surface, not the cause.

Running on the current major cleanly

Cannot find module '@storybook/addon-essentials/preview'

Addons will not resolve

Essentials was restructured across recent releases, and old import paths or addon-knobs references still linger in main.js or preview.js.

Addons consolidated and resolving

chromatic: 42 visual changes detected

Visual regression is blocking every PR

A font update, a new icon pipeline or a changed baseline has made Chromatic flag every story, and nobody is reviewing them because the list is overwhelming.

Baselines accepted, noise filtered

react-docgen-typescript: Failed to parse

Controls panel is empty for TS components

A component uses a generic, a union type or a re-exported prop interface that the TypeScript docgen parser cannot resolve, so Storybook does not know what controls to render.

Docgen working, controls populated

SB_DEPS: multiple versions detected

Storybook dependencies have drifted

Peer dependencies between the core, the framework preset and addons have fallen out of alignment, and the preview and manager load different versions of the same package.

Dependencies aligned, one version each

You cannot create a decorator inside a preview.js

Decorators throw on startup

An older decorator pattern is not compatible with the current preview runtime, or a global decorator is defined at the wrong level of the config.

Decorators on the current API

Vite build failed with 240 unresolved imports

Storybook on Vite cannot resolve project imports

The Vite builder is not inheriting aliases, SVG imports or custom loaders from the main app, so every project-specific import path fails.

Builder sharing project resolution

build-storybook: 412s

The static build is painfully slow

Hundreds of stories, autodocs on everything, and MDX pages with heavy imports stacking up, with no caching between CI runs.

Build time back to a few minutes

What we do

Storybook help, from upgrade to stable catalogue

Call us for one broken upgrade, or hand us the whole component catalogue.

Rescue
A Storybook that will not boot, a build that will not finish, or a Chromatic check that flags every story. We get it green before we decide what to change next.
Major version upgrades
Full upgrade from 6.5 or 7 to the current major, with addon compatibility, builder swap, API migration and a verified visual baseline afterwards.
Design system setup
First-time Storybook rollout for a new or existing component library, including autodocs, theme tokens, controls, a11y and visual testing wired in.
Visual testing
Chromatic, Percy or Playwright snapshots integrated with your PR flow, with baselines managed and false positives filtered.
Performance
Trimming addons, isolating the heavy stories, enabling caching, and keeping the build inside a sensible CI budget.
Managed Tech
An engineer on hand for minor upgrades, addon churn and the quiet regressions that creep in as the catalogue grows.

How it works

From first message to fixed

  1. Look Free estimate

    Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.

  2. Fix

    We fix the cause, not the symptom. If something is down, getting it back up comes first.

  3. Harden

    Backups, monitoring, updates and access, so the same problem can't quietly come back.

  4. Hand back or stay on

    You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.

Often found together

Running Storybook alongside something else?

We work on the whole stack, so the problem can be wherever it actually is.

Questions

Storybook questions

Something else? Call+1 737 727 7327

Can you upgrade our Storybook from an older major?

Yes. We branch the project, update core packages together, migrate each addon against the compatibility table, convert preview and manager files to the current API, run the full story catalogue, and only merge once the build and visual baseline look right. Most upgrades take between two and five days depending on addon count.

Why is our Storybook build so slow?

Usually a combination of autodocs rendering every component, MDX pages pulling in large dependencies, addons that run on every story, and no build caching. We profile the build, cut what is not pulling its weight, and typically bring the time down to a quarter of what it was.

Should we switch Storybook from Webpack to Vite?

In most cases yes, especially on projects where the app itself already runs on Vite. Startup times drop, HMR works, and the config surface shrinks. Projects leaning on bespoke Webpack loaders should expect to port those explicitly before the swap is complete.

Can you wire up Chromatic or Percy for us?

Yes. We set up the account, add the GitHub Actions or CI integration, generate the first baseline on your main branch, and tune the ignore patterns so the team only reviews real visual changes rather than animation frames and spinner timing.

Our controls panel is empty on TypeScript components. Why?

The TypeScript docgen parser Storybook uses struggles with certain generic, union and re-exported types. We either simplify the component types in that one area, swap the docgen implementation to react-docgen, or write explicit argTypes for the affected stories.

How much does Storybook help cost?

A quote costs nothing. Share the Storybook config and the failing log, and a written price arrives before any changes land in your repo.

Free estimate

Storybook misbehaving?

Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.

  • No charge to find out what it will take
  • If it's urgent, say so

Replies come from a person. By sending, you authorize us to email you back. No marketing.