Upgrade to 6.2.1 caused WSOD

Describe the bug I’ve upgraded from 6.1.11 to 6.2.1 without changing any config, and now starting it causes a WSOD. Here it is: Storybook.zip

I see that when going to localhost:6006 (where it runs) it redirects to localhost:6006/?path=/settings/release-notes which is probably not correct. That is not the starting page that it always used to be.

To Reproduce Steps to reproduce the behavior:

1. Have 6.1.11 installed
2. Upgrade
3. ???

Expected behavior Should keep working

Screenshots No screenshot, it’s a literal white blank screen with absolutely nothing visible, apart from white pixels (and a lot of them).

System Please paste the results of npx sb@next info here.

  System:
    OS: Windows 10 10.0.19042
    CPU: (12) x64 Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz
  Binaries:
    Node: 14.16.0 - C:\Program Files\nodejs\node.EXE
    npm: 6.14.11 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 89.0.4389.114
    Edge: Spartan (44.19041.423.0), Chromium (89.0.774.63)
  npmPackages:
    @storybook/addon-docs: 6.2.1 => 6.2.1
    @storybook/addon-links: 6.2.1 => 6.2.1
    @storybook/addons: 6.2.1 => 6.2.1
    @storybook/react: 6.2.1 => 6.2.1

┆Issue is synchronized with this Asana task by Unito

[seferturan]

Not really a useable workaround in my case, but maybe it’ll help with tracking down the issue:

Upgrading Storybook from 6.1.21 to 6.3.0 also resulted in a WSOD. But, downgrading react from 17.0.2 to 16.14.0 does get rid of the WSOD. Which feels weird, since none of my stories use react components (I’m using @storybook/html).

Just having react 17.0.2 seems enough to result in a WSOD, because even if I remove all react code from the codebase, it still results in a WSOD.

[shilman]

@thany I’m going to keep this issue open since it seems other people are hitting the problem. Perhaps we can figure out a more reliable workaround.