CodeVetter · Repo Unpack · System map
storybookjs/storybook
The product separates Node configuration and build orchestration from browser navigation and component execution. Framework presets select builders and renderers, while the published core package supplies shared APIs and runtime infrastructure. State spans browser storage, runtime service state, generated static artifacts, and a local instance registry. Contributor tooling and agent evaluation form separate workspace concerns.
- The Yarn workspace includes agent-eval, code/core, addons, builders, frameworks, renderers, libraries, presets, and scripts; the root pins yarn@4.18.0.
- dispatcher.ts imports the bundled core binary for dev/build/index/ai/tools/skills, routes init to create-storybook, and routes other commands to @storybook/cli.
- Core separates server orchestration, manager UI/API, preview rendering/API, channels, AST tooling, and testing support; its package exports distinguish source resolution from published dist modules.
- The React-Vite framework selects @storybook/builder-vite and @storybook/react/preset; builder-vite serves transformed iframe.html and installs Vite middleware.
- storybookDevServer creates a Polka application, installs Host/access/cache middleware, registers index.json, and starts manager and preview builders on the same HTTP server.
- Static builds emit manager and preview assets, index.json, optional project.json, service snapshots, and feature-gated manifests into the selected output directory.
- Storage boundaries include manager local/session storage, JSON service snapshots under outputDir/services, and runtime instance records under the user's .storybook/instances directory.
- NX compiles dependency packages before consumers and defines cached checks; agent-eval separately exposes experiment, comparison, analysis, and Next.js playground build commands.