Describe the bug
I recently updated @storybook/react and react-scripts, and now I cannot start storybook.
With @storybook/[email protected] and [email protected], I get the error presented on the screenshot. Changing back to [email protected] though works fine.
To Reproduce
Steps to reproduce the behavior:
@storybook/[email protected] and [email protected],Expected behavior
Should not crash.
Screenshots
If applicable, add screenshots to help explain your problem.

System:
System:
OS: Linux 5.0 Ubuntu 19.04 (Disco Dingo)
CPU: (4) x64 Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz
Binaries:
Node: 10.16.3 - ~/.nvm/versions/node/v10.16.3/bin/node
Yarn: 1.17.3 - ~/.yarn/bin/yarn
npm: 6.9.0 - ~/.nvm/versions/node/v10.16.3/bin/npm
Browsers:
Chrome: 77.0.3865.90
Firefox: 69.0.1
npmPackages:
@storybook/react: ^5.2.1 => 5.2.1
Additional context
I am uncertain if this is an issue with storybook or CRA.
Having the same issue.
As stated, downgrading react-scripts to 3.0.1 works
Hi @0tho, have you tried (while on the newer react-scripts) removing your node_modules and lockfile, and reinstalling?
Hi @mrmckeb - I'm having the same issue, and a reinstall didn't fix things.
My error is different, however:
Uncaught (in promise) TypeError: Cannot convert undefined or null to object
at Function.entries (<anonymous>)
at vendors~main.cff839a2a50bbfd2c813.bundle.js:8101
at memoizerific (vendors~main.cff839a2a50bbfd2c813.bundle.js:67932)
...
Do let me know if this feels separate to this issue and I'll add a new one!
Are you able to share that repo with me @calumgunn?
@mrmckeb Sadly not as it's in a private repo... I'll try to find time to create a minimal reproduction today.
@mrmckeb deleting node_modules, lockfile and reinstalling didn't solve the problem. (tried both npm and yarn)
I also can't share my main repo, but I will try to create a minimum project later.
I believe this error could be related to this
Thanks, reproductions are very valuable - and I understand that you can't always share a project.
@0tho, if you're issue is related to the issue you linked to, that has been resolved... I'll ask for a patch release.
@mrmckeb updated to [email protected] and for me it has fixed the problems.
Hi everyone! Seems like there hasn't been much going on in this issue lately. If there are still questions, comments, or bugs, please feel free to continue the discussion. Unfortunately, we don't have time to get to every issue. We are always open to contributions so please send us a pull request if you would like to help. Inactive issues will be closed after 30 days. Thanks!