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
In my project, I are using two different configurations of Storybook. One configuration uses the [name].stories.tsx file, while the other uses [name].test.stories.tsx. I encountered an issue when trying to dynamically import stories from [name].stories.tsx into [name].test.stories.tsx. While everything works fine during development, the build process results in an infinite loading state for the pages where this dynamic import is used.
The issue occurs only when using dynamic import. Static imports do not cause this issue.
The problem arises specifically when importing story files associated with a different Storybook configuration. For example, importing from [name].stories.tsx to [name].stories.tsx or from [name].test.stories.tsx to [name].test.stories.tsx does not cause any issues.
The issue is not present during development but only appears after the build process.
The text was updated successfully, but these errors were encountered:
Describe the bug
In my project, I are using two different configurations of Storybook. One configuration uses the
[name].stories.tsx
file, while the other uses[name].test.stories.tsx
. I encountered an issue when trying to dynamically import stories from[name].stories.tsx
into[name].test.stories.tsx
. While everything works fine during development, the build process results in an infinite loading state for the pages where this dynamic import is used.Reproduction link
https://github.com/yuheiy/storybook-issue-infinite-loading-state-when-using-dynamic-import-between-storybook-files
Reproduction steps
[name].stories.tsx
file.[name].test.stories.tsx
file.[name].test.stories.tsx
to load stories from[name].stories.tsx
.Button.stories.ts
:Button.test.stories.ts
:System
Additional context
[name].stories.tsx
to[name].stories.tsx
or from[name].test.stories.tsx
to[name].test.stories.tsx
does not cause any issues.The text was updated successfully, but these errors were encountered: