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
Running Storybook?
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.
What it is
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.
The honest version
No technology is all upside. This is where Storybook earns its place and where it tends to cause trouble.
Sound familiar?
The Storybook problems that bring people to us, and what you have once each one is fixed.
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
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
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
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
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
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
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
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
Call us for one broken upgrade, or hand us the whole component catalogue.
How it works
Tell us what's going wrong. We look at it, then tell you plainly what's wrong and what it will cost.
We fix the cause, not the symptom. If something is down, getting it back up comes first.
Backups, monitoring, updates and access, so the same problem can't quietly come back.
You get a plain-language write-up. Or we stay on for hosting, upkeep and new work.
Often found together
We work on the whole stack, so the problem can be wherever it actually is.
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.
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.
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.
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.
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.
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
Tell us what you're running and what's going wrong. A person reads it and comes back with an estimate.
Your message is with a real person, and we'll get back to you soon.
Rather talk now? Call us: