You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a tracking issue for officially deprecating @storybook/addon-storyshots.
Problem
Storyshots was replaced by the Test Runner over 1.5y ago but we are still supporting it via Github issues (12+ open, 300+ closed) & also via the feature flag storyStoreV7 disabled, which is a performance and maintenance problem for Storybook core.
Additionally, Storybook 8 will fully embrace storyStoreV7 and its on-demand architecture, meaning it will be the only option. Storyshots is incompatible with such architecture.
This project aims to provide a migration path for users who want to keep testing their stories successfully in Storybook 8, and hopefully get a better, more future proof experience.
Solution
The content you are editing has changed. Please copy your edits and refresh the page.
Describe the bug
This is a tracking issue for officially deprecating
@storybook/addon-storyshots
.Problem
Storyshots was replaced by the Test Runner over 1.5y ago but we are still supporting it via Github issues (12+ open, 300+ closed) & also via the feature flag storyStoreV7 disabled, which is a performance and maintenance problem for Storybook core.
Additionally, Storybook 8 will fully embrace storyStoreV7 and its on-demand architecture, meaning it will be the only option. Storyshots is incompatible with such architecture.
This project aims to provide a migration path for users who want to keep testing their stories successfully in Storybook 8, and hopefully get a better, more future proof experience.
Solution
Documentation
Core
sb extract
command #24653To Reproduce
No response
System
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: