Episode

Jeppe Reinhold - Storybook Modernization

Podcast
devtools.fm: Developer Tools, Open Source, Software Development
Published
Jan 5, 2026
Duration seconds
3329
Processing state
processed
Canonical source
https://podcasters.spotify.com/pod/show/devtoolsfm/episodes/Jeppe-Reinhold---Storybook-Modernization-e3d641s
Audio
https://anchor.fm/s/dd6922b4/podcast/play/113495548/https%3A%2F%2Fd3ctxlq1ktw2nl.cloudfront.net%2Fstaging%2F2026-0-4%2F415482577-44100-2-344a1fa3f784f.m4a
JSON
/v1/public/podcasts/devtools-fm/episodes/jeppe-reinhold-storybook-modernization
Markdown
/podcast/devtools-fm/jeppe-reinhold-storybook-modernization.md

Actions

  • POST https://stenobird.com/v1/public/podcasts/devtools-fm/episodes/jeppe-reinhold-storybook-modernization/transcription-requests
    Idempotently request low-priority transcript generation for this episode.
  • GET https://stenobird.com/podcast/devtools-fm/jeppe-reinhold-storybook-modernization.md
    Read the agent-friendly Markdown representation of this episode resource.

Summary

Storybook has undergone a massive architectural overhaul to move from a slow, complex tool to a high-performance development environment. Core contributor Jeppe Reinhold explains the transition from Webpack to Vite, the migration to ESM, and how AI agents will soon use MCP servers to interact with component libraries.

Topics

  • Storybook
  • Vite
  • ESM
  • Frontend Development
  • Chromatice
  • Vitest
  • AI Coding Agents
  • MCP Server
  • Open Source
  • Component Driven Development

Highlights

  • Main idea: The shift from Webpack to Vite was the primary driver in achieving near-instant Storybook startup times
  • Technical achievement: The team successfully migrated the core to ESM, eliminating CommonJS dependencies and reducing package bloat
  • Practical takeaway: Integrating Vitest allows developers to run component interaction tests locally, not just in CI/cloud environments
  • Future trend: Storybook is building MCP (Model Context Protocol) servers to allow LLM-based coding agents to understand and write stories automatically
  • Failure mode: High friction in initial Storybook setup and manual story creation remains a barrier to widespread adoption in large-scale applications

Chapters

  1. 1:00 Introduction to Jeppe Reinhold: Jeppe introduces his role at Chromatic and his work as a core contributor to the Storybook open-source project.
  2. 5:05 The Move to Vite and Slimming the Core: A discussion on reducing dependency bloat and the performance benefits of moving from Webpack to Vite.
  3. 9:25 Component Isolation and Testing: The importance of using Storybook as a unit view for components to test props and states in isolation.
  4. 13:45 Framework Agnosticism and CSF: The challenges of maintaining a format that supports diverse frameworks like React and Svelte.
  5. 21:50 The Complexity of ESM Migration: The technical debt and 'tiny annoyances' involved in removing CommonJS and handling module loading compatibility.
  6. 34:10 Vitest Integration and Local Testing: How bringing interaction testing to the local development loop improves the developer experience.
  7. 38:10 AI, MCP, and the Future of Storytelling: Exploring how coding agents will use MCP servers to discover components and automatically generate stories.