Introducing a new way to review your PRs.

Read the announcement

storybookjs / storybook

Storybook is the industry standard workshop for building, documenting, and testing UI components in isolation

View on GitHub

20 documents · Updated Nov 20, 2026

docs / project-setup-and-migration

Project setup and migration

Storybook setup and migration tools help a project reach a working Storybook configuration and keep it valid as Storybook changes. The setup flow detects the project environment and adds the right files and packages. The migration flow updates configuration and story code across one or more Storybook projects, then checks the result.

Related pages: Developer workflows, Testing fixtures and sandboxes, Repository automation, Agent evaluation platform, Ecosystem quality assurance, and CLI and server lifecycle.

Setup lifecycle

The create-storybook package provides the initialization path for a new or existing application. It turns a project directory into a Storybook project while keeping framework choice, language, builder, selected features, and package manager aligned. The orchestration also keeps dependency installation ahead of generator post-install work and addon setup.

Project bootstrapping

Project bootstrapping starts with basic checks before Storybook changes the project. If the directory is empty, the flow can create a supported application first. It then selects a package manager, checks the Storybook version, and prepares the project for initialization.

The flow can run interactively or in a non-interactive mode. A forced project type or package manager can replace discovery when the project needs an explicit choice. Agent mode also supports automated initialization and can write a diagnostic log for later review.

flowchart TD
    A[Project directory] --> B[Preflight checks]
    B -->|empty| C[Create application]
    B -->|has project| D[Use existing application]
    C --> E[Select package manager]
    D --> E
    E --> F[Detect project environment]
    F --> G[Generate Storybook setup]
    G --> H[Install packages]
    H --> I[Run post-install work]
    I --> J[Configure addons]

References: code/…/PreflightCheckCommand.ts• L21-107 code/…/scaffold-new-project.ts• L104-207 code/…/run.ts• L22-134 code/…/initiate.ts• L75-108 code/…/initiate.ts• L146-187

Environment discovery

Environment discovery identifies the project type and the language used by the project. It uses package metadata and known project markers to distinguish supported frameworks. The CLI keeps framework names and their Storybook packages as one set of setup choices, so discovery and user-selected setup use the same framework vocabulary. The selected generator supplies the renderer and any fixed or dynamic framework choice, while the CLI builder option takes precedence over detected or generator-provided builder settings.

Builder discovery checks project configuration and installed packages. One clear result is used directly. Multiple or missing results require a user choice unless the command supplies an override. Existing Storybook configuration also prevents an accidental second initialization unless the user forces it. Astro projects are recognized from the Astro dependency and use the Astro project type rather than the more general React path.

References: code/…/modernInputs.ts• L1-76 code/…/ProjectTypeService.ts• L49-174 code/…/ProjectTypeService.ts• L195-235 code/…/FrameworkDetectionService.ts• L16-86 code/…/ProjectDetectionCommand.ts• L33-56 code/…/FrameworkDetectionCommand.ts• L25-89

Framework generation

Framework generation maps the detected environment to a framework generator. Each generator declares the environment it supports and returns the setup choices needed for that environment. This lets the shared setup flow support many frameworks without changing its overall lifecycle.

The generator contract also covers framework-specific package and addon needs, configuration placement, and work that runs before or after installation. The registry is the boundary between environment discovery and framework-specific setup.

The generator creates the Storybook configuration and any framework-specific project files. It also records the packages and addons that the later install step must add. React Native is a special case: its generator creates platform entry points and launch scripts, prepares Metro integration, and uses a React Native Storybook directory instead of the shared web setup. Expo projects receive an extra dependency alignment step after installation. Astro uses a dedicated generator with Vite as its builder, adds the Vite builder package, and does not add example components because the Astro framework package provides none.

References: code/…/modernInputs.ts• L28-52 code/…/registerGenerators.ts• L1-50 code/…/index.ts• L6-19 code/…/GeneratorRegistry.ts• L7-30 code/…/types.ts• L72-137 code/…/GeneratorExecutionCommand.ts• L21-71 code/…/index.ts• L99-210

Configuration assembly

Configuration assembly produces the main and preview Storybook configuration for the selected language and renderer. The main configuration points to the project’s story and documentation files. The preview configuration provides shared story behavior when the framework template does not already provide one.

The generated configuration can use the framework’s CSF factories when that framework supports them. In this mode, the main and preview files use the framework-provided configuration entry points. Otherwise, setup keeps the standard configuration shape and uses the framework’s type information where available. This gives supported frameworks a shared typed configuration model without forcing the same shape on unsupported frameworks.

The result is a project-level Storybook configuration that matches the selected framework. Feature choices can add related story patterns and addons without changing the basic project shape. React Native returns its own configuration directory and does not start the web development command, because the app runs through platform scripts.

References: code/…/configure.ts• L49-123 code/…/configure.ts• L126-199 code/…/csf-factories.ts• L10-51 code/…/index.ts• L170-200

Story preview imports

Story preview imports connect copied example stories to the preview configuration generated for their destination. The setup tools identify supported story files and rewrite imports when the copied story location differs from the new preview location. This keeps generated examples usable when a framework uses the CSF factory setup.

The rewrite is limited to recognized story file types and known preview import patterns. Frameworks without the needed factory exports do not use this path, so they keep their existing story format.

References: code/…/csf-factories.ts• L7-8 code/…/csf-factories.ts• L54-105

Dependency installation

Dependency installation collects package changes during generation and applies them as one project update. It installs the collected packages unless the user selects the skip-install mode. A generator post-install step runs only after a successful install, so tools supplied by new dependencies are available. Addon configuration then runs after installation so addon tools can use the packages that are now available.

Community framework packages are released outside this repository. Stable Storybook releases install their latest package tag. A prerelease uses next only when that tag exists and is newer than latest; otherwise setup uses latest. An explicit package version remains unchanged.

The final setup reports the Storybook command and any incomplete addon work. This keeps package changes and configuration changes in a known order and gives the user a path to finish a partial setup.

References: code/…/DependencyInstallationCommand.ts• L15-101 code/…/AddonConfigurationCommand.ts• L26-76 code/…/initiate.ts• L138-187 code/…/community-frameworks.ts• L11-24 code/…/community-frameworks.ts• L31-84 code/…/index.ts• L202-211

Migration lifecycle

The @storybook/cli package coordinates version upgrades and targeted migrations. It can find Storybook projects in a workspace, update package versions, apply safe configuration changes, and report issues that still need attention.

Project collection

Project collection builds the input for an upgrade from Storybook configuration directories. It looks for standard Storybook directories in the workspace and reads the installed Storybook version, configuration, and story paths for each project.

The search covers both .storybook and React Native .rnstorybook directories while ignoring dependency folders. This model lets one upgrade command handle a single project or several projects. Each project keeps its own package manager and configuration context while the CLI presents one overall result.

flowchart LR
    A[Workspace] --> B[Find Storybook projects]
    B --> C[Read versions and config]
    C --> D[Check upgrade blockers]
    D --> E[Update dependencies]
    E --> F[Run automigrations]
    F --> G[Install dependencies]
    G --> H[Configure deferred addons]
    H --> I[Run doctor checks]

References: code/…/util.ts• L90-92 code/…/util.ts• L213-236 code/…/util.ts• L251-274 code/…/upgrade.ts• L354-423

Upgrade blockers

Upgrade blockers are checks that stop an automatic upgrade when a known project condition needs a human decision. Project collection runs them for a usable configuration unless the user forces the upgrade, then passes their results to the upgrade flow before package and file changes begin.

The blockers cover removed accessibility vision simulations, package-manager overrides that exclude the target Storybook version, and environment dependencies that no longer meet Storybook’s support floor. They also stop upgrades that still use the removed @storybook/test-runner. Each blocker reports the affected project and gives manual guidance instead of guessing at changes that could alter snapshots, dependency resolution, or test behavior.

Dependency checks cover shared framework packages such as React, Vite, Next.js, Angular, Preact, Svelte, and Vue. Some floors apply only when a related Storybook addon is present, such as Vitest with @storybook/addon-vitest or SvelteKit with @storybook/sveltekit. Package metadata can also describe the version bundled by tools such as Vite+, so the check evaluates the effective framework version rather than only the wrapper package version. React experimental builds with a 0.0.0 version are treated as supported modern builds.

The test-runner check fires when @storybook/test-runner is listed in the project or is installed without being listed. The upgrade message directs the user to replace it with @storybook/addon-vitest or stay on Storybook 10. Blocker messages from several projects are grouped by message and list the affected configuration directories. The --force option skips these checks when the user accepts the risk.

The vision check only applies when the accessibility addon is active. It examines preview globals and story globals for the removed protanomaly, deuteranomaly, and tritanomaly values. The user must remove the value or choose a replacement because each replacement can change visual output.

References: code/…/util.ts• L342-358 code/…/index.ts• L9-43 code/…/block-dependencies-versions.ts• L6-65 code/…/block-dependencies-versions.ts• L66-137 code/…/block-test-runner.ts• L5-27 code/…/block-a11y-vision-simulations.ts• L36-80 code/…/block-storybook-overrides.ts• L10-20 code/…/utils.ts• L26-61 code/…/utils.ts• L71-132

Version upgrade

Version upgrade moves Storybook packages to the version represented by the running CLI. It checks that the target is not an unsupported downgrade and can stop when project-level blockers prevent a safe change. It updates package manifests before migration checks use the new version. Package installation can retry npm peer conflicts with safer fallback modes, and monorepos can receive dependency deduplication.

After the package update, the CLI runs automigrations and installs dependencies for the selected projects. Addons that require installed packages are configured after that install. The CLI then runs health checks and reports successful projects, failed projects, and projects with no applicable fixes.

References: code/…/upgrade.ts• L402-475 code/…/upgrade.ts• L493-555 code/…/util.ts• L169-194

Automigration selection

Automigrations are named fixes that detect whether a project needs a change. A fix can update files, adjust dependencies, or report a manual action. The CLI checks fixes against each project before it asks the user to select applicable changes.

The same fix can run across several projects. Dry-run mode reports the planned changes without writing them. Non-interactive mode selects fixes according to their default policy, while an explicit fix name can run a targeted migration.

The fix registry includes migrations for the Vitest setup contract and the SvelteKit mock contract. These fixes use project context to decide when an automatic edit is safe. They leave uncertain cases unchanged and give the user a manual path instead of guessing.

Some fixes protect dependency contracts needed by Storybook features. During the Storybook 11 peer-dependency change, a supported renderer can receive the TypeScript package needed for docgen. A TypeScript 7 project that lacks the compiler API receives manual guidance to keep a TypeScript 6 package available instead of an automatic package rewrite. A React project crossing the same change can receive a temporary react-docgen fallback when the effective TypeScript version for docgen cannot use the server API. The check uses typescript.docgenSpecifier when the project sets it; otherwise it uses the declared TypeScript version. Projects with the relevant docgen controls or an existing react-docgen dependency are left alone.

Storybook 11 migrations also remove the obsolete features.argTypeTargetsV7 and features.disallowImplicitActionsInRenderV8 flags. The fix applies only when the project targets Storybook 11 or later, keeps other feature settings, and stops when a spread makes the feature object unsafe to edit automatically.

References: code/…/types.ts• L51-117 code/…/index.ts• L117-233 code/…/multi-project.ts• L59-197 code/…/multi-project.ts• L226-300 code/…/index.ts• L37-68 code/…/vitest-setup-file.ts• L74-89 code/…/sveltekit-mocking-before-each.ts• L46-81 code/…/typescript-dependency.ts• L15-81 code/…/typescript-7-react-docgen.ts• L11-66 code/…/docgen-typescript.ts• L1-28 code/…/remove-legacy-feature-flags.ts• L4-33 code/…/remove-legacy-feature-flags.test.ts• L76-186

Configuration migration

Configuration migration applies changes to Storybook main, preview, manager, and story files through a shared file pass. The migration system classifies files by role and lets each fix use either text changes or parsed Storybook configuration and story data.

The runner writes a file only when a fix changes it. A failure is recorded for the affected file and fix. A failure in a main configuration file prevents that fix from continuing across the rest of the project, which protects the project from a partial configuration update.

The current fixes include targeted migrations for framework configuration, story syntax, test setup, and removed framework-specific APIs. Their common goal is to preserve behavior while moving setup from an old contract to the contract expected by the new Storybook version.

References: code/…/pipeline.ts• L20-62 code/…/pipeline.ts• L120-160 code/…/pipeline.ts• L163-275 code/…/index.ts• L37-68

Vitest setup migration

The Vitest setup migration removes obsolete setProjectAnnotations calls when the Storybook Vitest plugin or addon now applies those annotations itself. It can remove an empty setup file, remove its setupFiles entry, or keep unrelated setup code.

The fix checks shared Vitest projects, config inheritance, setup file paths, and registered addons before editing. If a setup file may still serve portable stories or contains custom annotations, it reports manual instructions and leaves the project unchanged.

References: code/…/vitest-setup-file.ts• L74-225 code/…/vitest-setup-file.ts• L227-305 code/…/vitest-setup-file.test.ts• L174-316 code/…/vitest-setup-file.test.ts• L648-816

SvelteKit mock migration

The SvelteKit mock migration moves the removed parameters.sveltekit_experimental contract into Storybook beforeEach hooks and the current SvelteKit mock modules. It covers preview files, standard CSF stories, and Svelte CSF stories. It also keeps the old merge behavior across preview, meta, and story levels when that behavior can be read safely.

The migration accounts for docs pages because inline stories share mock state. It adds the needed iframe setting when it can do so safely. Dynamic values, spreads, ambiguous inheritance, and code that reads the removed parameter produce a file-level manual failure rather than a partial rewrite. The Svelte parser is loaded from the project so the migration follows the project's Svelte syntax.

References: code/…/sveltekit-mocking-before-each.ts• L46-111 code/…/csf-files.ts• L369-433 code/…/csf-files.ts• L531-588 code/…/svelte-stories.ts• L42-164 code/…/migrate-levels.ts• L83-140 code/…/svelte-csf-file.ts• L94-121 code/…/sveltekit-mocking-before-each.test.ts• L99-212 code/…/sveltekit-mocking-before-each.test.ts• L1028-1115

Codemod execution

The CLI's migrate command provides named source transforms for common story migrations. It validates the transform name, selects files with a glob or an explicit path list, and reports transformed, unchanged, and failed files.

The shared codemod runner supports dry runs and skips dependency and generated-output directories. It processes files with bounded parallel work and writes only changed results. A requested suffix rename runs only after every transform succeeds, so a failed migration does not leave a partly renamed story set.

References: code/…/migrate.ts• L5-71 code/…/codemod.ts• L11-18 code/…/codemod.ts• L34-120 code/…/codemod.test.ts• L17-29 code/…/migrate.test.ts• L49-177

CSF factory migration

The CSF factory migration moves eligible stories and their main and preview configuration to the CSF 4 factory form. It can first bring older CSF stories to a usable shape, then add preview imports and update configuration while preserving framework-specific choices.

The command can use relative imports or documented subpath imports. Sandbox and React Native projects use controlled import behavior because their preview paths have special constraints. Files that the transform cannot safely convert remain unchanged for review.

References: code/…/csf-factories.ts• L25-39 code/…/csf-factories.ts• L46-79 code/…/csf-factories.ts• L82-179 code/…/csf-factories-utils.ts• L102-148 code/…/remove-unused-types.ts• L31-109 code/…/csf-factories.test.ts• L12-101

Migration completion

Migration completion installs packages added by fixes and configures addons that must run after installation. It also refreshes Storybook agent skills when the project already uses them, or refreshes agent instructions when it does not. The CLI then runs Storybook doctor for each selected project and combines the results with automigration status.

The final report separates successful projects, failed projects, and projects that needed no fixes. This distinction matters because a project can finish with no migration work or with health issues even when its file changes succeeded.

References: code/…/index.ts• L79-113 code/…/upgrade.ts• L529-583 code/…/upgrade.ts• L163-229

Supporting discovery tools

The CLI also includes tools that make setup and migration easier to inspect. They create controlled project inputs, connect local Storybook code to reproductions, and explain package or configuration problems after a change.

Sandbox creation

The sandbox command creates a small project from a known framework template. It is intended for a minimal reproduction of a Storybook issue or for checking a setup path outside a user project. A sandbox can contain only the base application or can run Storybook initialization as part of its creation.

Template metadata records the expected framework, renderer, and builder. This makes the sandbox useful as a discovery aid because a generated project can be checked against the environment that the setup flow should detect.

References: code/…/sandbox.ts• L35-57 code/…/sandbox.ts• L129-235 code/…/sandbox-templates.ts• L33-57

Repository linking

The link command connects a Storybook repository checkout to a reproduction project. It prepares the reproduction with the local packages, installs the result, and can start Storybook. This shortens the path from a reported issue to a project that exercises the local setup or migration code.

The command supports a local directory or a cloned reproduction. It requires Yarn Berry, which means Yarn 2 or later, so the local package links behave as expected. Before installation it adds the small compatibility dependencies needed by the linked project when they are absent.

References: code/…/link.ts• L9-24 code/…/link.ts• L31-70 code/…/link.ts• L73-106

Project health checks

Storybook doctor checks the state left by setup or migration. It reports missing Storybook packages, incompatible package relationships, mismatched versions, duplicated dependencies, and configuration errors.

It also checks package-manager overrides that pin core Storybook packages outside the installed version. It checks Storybook-like packages against the current core version and reports an available core update when a core package is newer than the current Storybook version. The doctor shows package incompatibility before version or duplicate-dependency warnings so the user can address the primary conflict first.

The doctor can inspect one project or combine repeated findings across several projects. Multi-project output groups the same diagnostic and names all affected projects. It is a diagnostic step rather than a migration step, so its result tells the user what still needs attention without silently changing the project.

References: code/…/types.ts• L16-53 code/…/index.ts• L60-163 code/…/index.ts• L192-240 code/…/index.ts• L242-369 code/…/getIncompatibleStorybookPackages.ts• L28-115 code/…/getIncompatibleStorybookPackages.ts• L118-178 code/…/getStorybookOverrides.ts• L22-39 code/…/getStorybookOverrides.ts• L54-129

Change checklist

When these files or sections are changed, remember to consider these:

  • A new or changed framework choice must stay aligned across the CLI inputs, project detection, generator registration, framework metadata, and the empty-directory scaffold choices.
  • A generator metadata or lifecycle change must preserve the boundary between environment discovery, configuration, dependency collection, and post-install work.
  • Community framework package registration must stay aligned with the framework package map, package versions, Nuxt package substitutions, and stable or prerelease dist-tag selection.
  • Changes to the setup order must preserve the dependency-install-before-addon-configuration contract.
  • Changes to framework factory support must keep the supported-framework list, generated main and preview shapes, and copied-story preview imports aligned.
  • A new migration fix must define its detection, selection policy, file scope, result status, and post-install behavior as one contract.
  • The Vitest setup fix must keep setup file resolution, project inheritance, Storybook plugin detection, addon registration, and manual fallback behavior aligned.
  • The SvelteKit mock fix must keep preview, meta, story, Svelte CSF, docs-page behavior, and manual-failure rules aligned.
  • A version-bound configuration cleanup must keep its version gate, registered fix, safe edit scope, and handling of unsupported config shapes aligned.
  • Changes to project discovery must keep standard config directories, custom config paths, and multi-project reporting consistent.
  • Changes to autoblockers must keep blocker registration, parallel result handling, force behavior, affected-file grouping, dependency floors, conditional addon gates, and manual migration guidance aligned.
  • Changes to dependency version checks must keep effective bundled-version lookup, prerelease handling, experimental React handling, and fail-open behavior for unknown gate versions aligned.
  • Changes to test-runner support must keep listed-dependency checks, installed-package checks, the Storybook 11 guidance, and the migration link aligned.
  • Changes to override or package compatibility checks must keep package-manager sources, Storybook core package recognition, version-range handling, and doctor diagnostic priority aligned.
  • Changes to codemod names or transform files must keep the CLI list, validation, parser choice, file selection, and published transform paths aligned.
  • Changes to the CSF factory command must keep story conversion, main and preview conversion, import-map choice, and sandbox path selection aligned.
  • Changes to TypeScript migration checks must keep renderer support, effective docgen TypeScript resolution including typescript.docgenSpecifier, dependency choice, fallback behavior, and the manual TypeScript 6 guidance aligned.
  • Changes to reproduction linking must preserve the Yarn Berry requirement and the dependencies needed by linked packages.

Important failure modes

TriggerConsequenceGuard
Storybook runs in an empty directory with Yarn 1Project creation can fail because the package layout is not supportedPreflight falls back to npm for empty-directory setup
Storybook finds an existing .storybook directory without --forceInitialization stops instead of overwriting an existing setupProject detection asks for confirmation and exits when the user declines
Builder detection finds several or no buildersThe generated framework choice may be wrongThe CLI asks the user to select a builder or accepts an explicit override
A framework is marked as factory-supported without the matching exportsGenerated configuration or story imports do not loadFactory support is limited to frameworks with the required main and preview entry points
A copied story keeps a source-relative preview importThe generated example can use the wrong preview configurationSetup rewrites recognized preview imports for supported story files
A prerelease community framework has no current next tag, or its next tag is older than latestSetup can select a package from the wrong release lineCommunity package selection falls back to latest unless next exists and is newer
A project uses a framework dependency below the Storybook support floorThe upgrade can install packages that no longer support the project environmentThe dependency blocker reports the package, installed version, minimum version, and migration guidance
@storybook/addon-vitest is present with Vitest below 4, or @storybook/sveltekit is present with SvelteKit below 3The addon and the upgraded Storybook can fail against the old test or framework contractConditional dependency floors run only when the related addon is installed
A project lists or installs @storybook/test-runnerThe test runner is incompatible with Storybook 11 and the upgrade can leave testing unusableThe test-runner blocker requires the Vitest addon migration or continued use of Storybook 10
A bundled tool reports its wrapper version instead of its effective Vite or Vitest versionA supported project can be blocked or an unsupported project can passDependency checks use bundled package versions when package metadata provides them
A dependency version lookup throws while checking a conditional addon floorThe upgrade may continue without a definitive conditional checkThe blocker fails open when gate versions cannot be determined and reports no blocker
A codemod name is not registeredThe requested migration cannot runThe CLI validates the name against its migration map
A codemod reports an error while suffix renaming is requestedFiles are transformed but not renamed, avoiding a mixed file setRenaming is skipped when any transform reports an error
A migration changes a main configuration file and then failsThe fix is marked failed and does not continue across the remaining project filesThe migration pipeline treats main-file failure as a fix-level stop
An accessibility story or preview uses a removed vision simulationVisual output can change after an automatic replacementThe autoblocker reports the files and requires a manual choice
A package-manager override excludes the target Storybook versionInstallation can keep an older core package or fail dependency resolutionDoctor and upgrade blockers list the override and require an update or removal
A Vitest setup file is shared with a project without the Storybook pluginRemoving setProjectAnnotations can break that other projectThe fix reports the file for manual migration
A Vitest setup path or project root is computed at runtimeThe fix cannot prove which file or project will loadThe fix leaves the files unchanged and reports manual steps
Storybook 11 or later retains a removed feature flag inside a spreadThe legacy-flag fix cannot safely edit the feature objectThe migration reports the fix failure instead of changing an ambiguous configuration
SvelteKit mock parameters use spreads, dynamic values, or reads of the removed parameterA partial rewrite can change mock state or story assertionsThe SvelteKit fix leaves the file unchanged and reports the exact manual issue
SvelteKit docs stories share mocks while docs render inlineStories can affect each other through shared mock stateThe migration adds docs.story.inline: false when safe, or reports a manual action
A React project uses a docgen TypeScript version without the required API and lacks react-docgen during the peer-dependency changeControls and the Docs args table can lose component type dataThe migration resolves the configured or declared docgen TypeScript version and offers the temporary fallback when applicable
A configured typescript.docgenSpecifier cannot be resolvedThe docgen fallback check is skipped and type data may remain unavailableThe helper returns no usable version instead of making an unsafe dependency change
Storybook packages use different versionsRuntime and addon behavior can become inconsistentUpgrade checks package consistency and doctor reports mismatches
A reproduction uses Yarn 1 or an older package managerLocal Storybook package links are not createdThe link command checks for Yarn Berry and stops with setup guidance

Key files

FileWhy to read it
code/…/initiate.tsMain setup orchestration from preflight through final reporting
code/…/run.tsPublic setup options, agent mode, logging, and command entry
code/…/PreflightCheckCommand.tsEmpty-project handling, package-manager setup, and version checks
code/…/modernInputs.tsSupported framework choices, display names, and Storybook package mapping
code/…/ProjectTypeService.tsProject and language discovery rules
code/…/FrameworkDetectionService.tsBuilder and framework discovery
code/…/FrameworkDetectionCommand.tsApplies CLI and generator builder choices before framework selection
code/…/types.tsContract between detected environments and framework generators
code/…/registerGenerators.tsFramework generator registration boundary
code/…/configure.tsGenerated main and preview configuration shapes
code/…/csf-factories.tsFramework support and copied-story preview import handling for CSF factories
code/…/index.tsAstro framework setup choices and Vite builder requirements
code/…/index.tsReact Native setup, Metro wiring, platform scripts, and Expo follow-up
code/…/GeneratorExecutionCommand.tsBoundary between generator choices and shared setup work
code/…/community-frameworks.tsCommunity framework package classification and stable or prerelease package tags
code/…/upgrade.tsMulti-project version upgrade lifecycle and final result reporting
code/…/index.tsRegistration and parallel execution of upgrade safety blockers
code/…/block-dependencies-versions.tsSupported framework and addon dependency floors for upgrades
code/…/block-dependencies-versions.test.tsGuarantees for dependency floors, conditional addon gates, bundled versions, and supported experimental builds
code/…/block-test-runner.tsDetects the removed test runner and gives the two supported paths forward
code/…/block-test-runner.test.tsGuarantees for listed and installed test-runner detection and migration guidance
code/…/utils.tsEffective package-version lookup and grouped blocker reporting
code/…/block-a11y-vision-simulations.tsDetects removed accessibility vision settings that need manual migration
code/…/block-storybook-overrides.tsConnects dependency overrides to the upgrade blocker flow
code/…/index.tsRegistry of automatic and command migrations
code/…/vitest-setup-file.tsVitest setup cleanup and safe manual fallback rules
code/…/sveltekit-mocking-before-each.tsSvelteKit mock migration entry point and safety checks
code/…/csf-files.tsShared Storybook config and CSF migration flow for SvelteKit mocks
code/…/svelte-csf-file.tsSvelte CSF discovery and source-preserving edits
code/…/typescript-dependency.tsTypeScript dependency checks, compiler API guidance, and the peer-dependency boundary
code/…/typescript-7-react-docgen.tsTemporary React docgen fallback for TypeScript 7.0 projects
code/…/docgen-typescript.tsResolves the TypeScript version used by docgen checks
code/…/remove-legacy-feature-flags.tsStorybook 11 cleanup for obsolete feature flags
code/…/remove-legacy-feature-flags.test.tsGuarantees for version gating, flag removal, and safe config editing
code/…/util.tsStorybook project discovery and project data collection
code/…/index.tsTargeted and automatic migration entry points
code/…/pipeline.tsShared file migration and failure behavior
code/…/migrate.tsCLI entry point for named codemods
code/…/codemod.tsShared file selection, transform execution, dry-run, and result reporting
code/…/csf-factories.tsCSF 4 story and configuration migration command
code/…/csf-factories-utils.tsPreview import and configuration property rules for CSF factories
code/…/remove-unused-types.tsRemoves obsolete Storybook type declarations left by factory conversion
code/…/index.tsHealth checks and single-project or multi-project diagnostics
code/…/getStorybookOverrides.tsFinds and explains overrides that exclude the target Storybook version
code/…/getIncompatibleStorybookPackages.tsFinds Storybook package relationships that do not match the current core version
code/…/sandbox.tsMinimal reproduction project creation
code/…/link.tsLinks local Storybook packages into a Yarn Berry reproduction