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
I have a project where we run storybook-react and storybook-html in the same repository.
Therefore I want to be able to start the storybook dev server for react and html in parallel on different ports:
storybook dev -p 3000 -c setup/storybook-react
storybook dev -p 3001 -c setup/storybook-html
But as soon as I start both dev servers I am seeing empty pages or JS errors.
My guess would be that there is some kind of shared cache in node_modules/.cache/storybook where both instances are overwriting necessary files of each other.
This is only an issue since Storybook 7 with the updated CLI tools. Before that it was possible to start both servers in parallel.
Describe the bug
I have a project where we run storybook-react and storybook-html in the same repository.
Therefore I want to be able to start the storybook dev server for react and html in parallel on different ports:
But as soon as I start both dev servers I am seeing empty pages or JS errors.
My guess would be that there is some kind of shared cache in
node_modules/.cache/storybook
where both instances are overwriting necessary files of each other.This is only an issue since Storybook 7 with the updated CLI tools. Before that it was possible to start both servers in parallel.
To Reproduce
No response
System
Additional context
No response
The text was updated successfully, but these errors were encountered: