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
Apperantly I have an issue running Storybook (version 6) with TypeScript using rollup.js through yarn build-storybook.
As long as I only include stories which relate to plain javascript-modules, everything runs fine. But as soon as I add a story, which releates to a typescript-module, the complete storybook is broken (means the skeleton is there, but waiting for content). Unfortunately without any error-message, that might help me out.
Does anyone know, where this might come from and what I can do as Storybook states on their website that there should be "zero-configuration" for typescript. Am I missing anything here?
Even stranger: if I run yarn start-storybook --node-resolve --watch --open everything works fine. How is this different? What mechanism is used here to compile typescript?
Apperantly I have an issue running Storybook (version 6) with TypeScript using rollup.js through yarn build-storybook.
As long as I only include stories which relate to plain javascript-modules, everything runs fine. But as soon as I add a story, which releates to a typescript-module, the complete storybook is broken (means the skeleton is there, but waiting for content). Unfortunately without any error-message, that might help me out.
Does anyone know, where this might come from and what I can do as Storybook states on their website that there should be "zero-configuration" for typescript. Am I missing anything here?
Even stranger: if I run yarn start-storybook --node-resolve --watch --open everything works fine. How is this different? What mechanism is used here to compile typescript?
Here comes my .storybook/main.js
package.json:
The text was updated successfully, but these errors were encountered: