Open futurethang opened 3 years ago
When I went from from 6.3.0-rc.11 -> 6.3.1, on Chrome specifically (which is what Storybook auto-opens on my machine) I experienced this going to http://localhost:6006/ - but http://localhost:6006/? then worked. Incognito window and other browsers worked without the query string. Hard refresh (cmd-shift-R) on the WSOD page fixed it in Chrome. I imagine something about my site headers allowed the browser to cache the page with no query string, which then pointed to the wrong assets when I upgraded versions.
This is a super-annoying issue that we experience over and over again every time we update Storybook. I know it can be easily fixed by hitting Ctrl+F5 but it's not obvious at all for somebody experiencing it for the very first time. And even when hit this problem for the second time, you might not remember the solution right away since dependencies are not being updated so often. I just want to say that with this issue not fixed, so much time of many developers is being wasted on such a stupid thing.
@livthomas any idea how to fix it?
@shilman I don't know what caching mechanism you've added recently (since this problem started to pop up just a few months ago). If it relies on some outdated files, you can remove those files in postinstall
git hook. And if it's caused by the way browsers work, you can try to force refresh the page automatically when Storybook is started for the first time after an update. Or add some kind of check to your service worker or whatever is being used there.
Describe the bug I know other issues are active, and so far I have not found working solutions for my case. I am also experiencing a blank white screen, with no terminal or browser console errors at all.
Project is built on Lit Element / Lit HTML
To Reproduce https://github.com/momentum-design/momentum-ui/tree/kehyde/storybook-upgrade/web-components
run
yarn install
runyarn storybook
System Please paste the results of
npx sb@next info
here.Additional context
main.ts:
manager.ts:
preview.ts: