Repository navigation
Custom Storybook version feature won't work for v8 #156
Description
Defining custom Storybook version done in #107 is capped at Storybook v8 due to breaking change in Storybook CLI.
It's mentioned in the PR, but I've done some digging and here's where it failed. Might not be the only blocker
Code:
Line 7 in 79c8568
Issue:
- -s $STORYBOOK_STATIC_PATHReference:
With the release of Storybook 8, the -s CLI flag was removed. We recommend using the static directory instead if you need to serve static files.
Source:
Activity
mrtimbrook commentedon Mar 20, 2026
Thanks for this. I'm going to find some time in the coming weeks to look into where the gaps are that prevent us from supporting newer versions of Storybook.
wojciechczerniak commentedon Mar 21, 2026
That may be a rabbit hole with so many versions ahead. If I may suggest, Blast is using server-webpack5 internally, and does a great job processing Blade into JSON configs. IMO that should be the main focus of Blast.
I would prefer a command
artisan blast:watchto run just the Blast watcher for Blade, and leave the Storybook configuration to me. Maybe a better configuration for output path. Endpoint url and path is all we need. As long as the JSON format won't change, all Storybook versions should work.You don't have to remove storybook, both approaches can work next to each other. It can be done without breaking change. Although, less moving parts, the easier to maintain the project and focus on stories syntax. Which btw works great.