storybook: Storybook stuck loading
Describe the bug In an attempt to update from 6.4.9 to 6.4.14, after building and opening the browser tab, Storybook initially loads into its loading state, but it’s stuck there. It never completes loading its UI, like this:

There are no build errors/warnings, no console errors and no meaningful warnings, and no network errors.
Only thin I can see is /progress which is presumably a part of Storybook, doesn’t finish loading.
I’ve also upgraded @storybook/preset-create-react-app from 3.2.0 to 4.0.0, and in the changelog, all I can see is support for CRA 5, which is all fine - I should assume CRA v4 is not removed, is it? Because that one hadn’t been upgraded. However, downgrading this package back to 3.2.0 works around the problem: Storybook 6.4.14 now loads correctly.
To Reproduce Follow the above description.
System
Please paste the results of npx sb@next info here.
System:
OS: Windows 10 10.0.19043
CPU: (12) x64 Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz
Binaries:
Node: 16.13.2 - C:\Program Files\nodejs\node.EXE
npm: 8.3.2 - C:\Program Files\nodejs\npm.CMD
Browsers:
Chrome: 97.0.4692.99
Edge: Spartan (44.19041.1266.0), Chromium (97.0.1072.62)
npmPackages:
@storybook/addon-a11y: 6.4.14 => 6.4.14
@storybook/addon-actions: 6.4.14 => 6.4.14
@storybook/addon-controls: 6.4.14 => 6.4.14
@storybook/addon-docs: 6.4.14 => 6.4.14
@storybook/addons: 6.4.14 => 6.4.14
@storybook/preset-create-react-app: ^3.2.0 => 3.2.0
@storybook/react: 6.4.14 => 6.4.14
@storybook/theming: 6.4.14 => 6.4.14
(How does this still manage to miss the one browser I’m actually using??)
Additional context Other packages noteworthy:
- Craco 6.2.0 - using Craco means we have no direct control over whichever CRA version it uses.
- Webpack 4.46.0 - Updating to 5.x gave us a myriad of weird problems, so we decided to stick with v4, which should be fine because that one isn’t EOL yet.
I’m in the process of updating (or trying to, honestly) our dependencies to their latest, and I would like small chunks of updates at a time. Updating too many packages in one go makes it difficult to diagnose problems. So yeah, I could also update Craco, but I don’t want to just yet, because it’s not only Storybook depending on it.
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Reactions: 16
- Comments: 33 (4 by maintainers)
This bug should not be closed. Storybook should output some reason as to why it is whitescreening.
There should be some error message from Storybook to help us identify what the problem is and what causes it.
For now and until Storybook take some action, we can use
git bisectto identify what commit caused this problem.I’m having the same issue and have deadline to deliver the storybook and I’m sooooo blocked 😦
Same issue.
With barebone
main.tsAnd barebone
preview.tsFor me this happens in a monorepo. When my story imports one of my monorepo packages/a component that uses that package, the storybook ends up infinitely loading. There is no error.
This should not be closed 😃 @shilman
I’m facing the same issue using: “@nrwl/storybook”: “15.3.0” “@storybook/addon-essentials”: “~6.5.9”, “@storybook/builder-vite”: “0.2.5”, “@storybook/core-server”: “~6.5.9”, “@storybook/react”: “~6.5.9”,
please reopen and fix the issue
@velidan 😦

@trainoasis I believe that loading error happens when you use
@storybook/preset-create-react-app@4withreact-scripts@4. If this matches your setup, either upgrade toreact-scripts@5or downgrade to@storybook/preset-create-react-app@3. More discussion #18221this issue is hitting people at random and is likely caused by corporate sabotage paid for by competition like figma. We have to wait for the developers to be not paid off to fix this one
agreed, same issue, please reopen. in my case it’s caused by passing a specific prop into the component, i have no clue why it’s causing this issue. zero logging whatsoever
Agree, it would be great with some error messages in the “infinite spinner” case. I’m trying to set up storybook for my project now, but after running into the infinite spinner I’m not sure how to proceed. (I probably have some problem with my Webpack config, but it’s hard to tell)
This happened to me on FF when I had too many storybook tabs open. I don’t know why, but opening in Chrome / closing all my FF tabs with SB in them made the whitescreening go away.
In my case all requests were rewritten to index.html. I added rewrite rule fore iframe.html
no way to understand what’s happened: ( sad