-
Describe the bugAfter succesfully updating Reproduction linknone Reproduction steps
SystemStorybook Environment Info:
System:
OS: Windows 11 10.0.26100
CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12700H
Binaries:
Node: 20.10.0 - C:\Program Files\nodejs\node.EXE
npm: 10.4.0 - C:\Program Files\nodejs\npm.CMD <----- active
Browsers:
Edge: Chromium (140.0.3485.54)
npmPackages:
@storybook/addon-a11y: ^9.1.8 => 8.4.7
@storybook/addon-designs: ^10.0.2 => 8.0.4
@storybook/addon-essentials: ^8.4.7 => 8.4.7
@storybook/addon-interactions: ^8.4.7 => 8.4.7
@storybook/addon-links: ^9.1.8 => 8.4.7
@storybook/blocks: ^8.4.7 => 8.4.7
@storybook/html: ^9.1.8 => 8.4.7
@storybook/html-vite: ^9.1.8 => 8.4.7
@storybook/test: ^8.4.7 => 8.4.7
storybook: ^9.1.8 => 8.4.7
storybook-addon-pseudo-states: ^9.1.8 => 4.0.2
storybook-dark-mode: ^4.0.2 => 4.0.2Additional contextStorybook 8.4.7 for html-vite |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
|
Hi @bourpie! I'm Dosu and I’m helping the storybook team. This is a known issue, especially on Windows and in PowerShell: the automigration process relies on interactive CLI prompts, which can hang indefinitely if the terminal doesn't fully support them. This often happens at the "Select automigrations to run" step and is not specific to html-vite or your project setup (reference). You can work around this by running the upgrade with the npx storybook@latest upgrade --yesIf that doesn't help, try running the command in a different shell (like Git Bash or WSL), or make sure your terminal supports interactive prompts. Other things to check:
If you still get stuck, you can manually follow the migration steps in the Storybook 9 migration guide and run To reply, just mention @dosu. How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other |
Beta Was this translation helpful? Give feedback.
-
|
@dosu Wow ! That was fast!! Your solution works perfectly ! Thank you ! |
Beta Was this translation helpful? Give feedback.
Hi @bourpie! I'm Dosu and I’m helping the storybook team.
This is a known issue, especially on Windows and in PowerShell: the automigration process relies on interactive CLI prompts, which can hang indefinitely if the terminal doesn't fully support them. This often happens at the "Select automigrations to run" step and is not specific to html-vite or your project setup (reference).
You can work around this by running the upgrade with the
--yesflag, which skips all prompts and should avoid the hang:If that doesn't help, try running the command in a different shell (like Git Bash or WSL), or make sure your terminal supports interactive prompts.
Other th…