Error with 5.1.0-beta and React < 16.6
See original GitHub issueDescribe the bug When using React < 16.6, storybook 5.1.0-beta fails to load in the browser with the following error in the dev console:
Uncaught TypeError: React.memo is not a function
at Object../node_modules/react-inspector/dist/cjs/react-inspector.js (vendors~main.346d12fabfecf4be4f79.bundle.js:115806)
at __webpack_require__ (runtime~main.346d12fabfecf4be4f79.bundle.js:782)
at fn (runtime~main.346d12fabfecf4be4f79.bundle.js:150)
at Object../node_modules/@storybook/theming/dist/convert.js (vendors~main.346d12fabfecf4be4f79.bundle.js:46334)
at __webpack_require__ (runtime~main.346d12fabfecf4be4f79.bundle.js:782)
at fn (runtime~main.346d12fabfecf4be4f79.bundle.js:150)
at Object../node_modules/@storybook/theming/dist/index.js (vendors~main.346d12fabfecf4be4f79.bundle.js:46851)
at __webpack_require__ (runtime~main.346d12fabfecf4be4f79.bundle.js:782)
at fn (runtime~main.346d12fabfecf4be4f79.bundle.js:150)
at Module../.storybook/theme.js (main.346d12fabfecf4be4f79.bundle.js:734)
I am upgrading from storybook 5.1.0-alpha.37
The React peerDependencies seem to suggest that any version is supported ("react": "*"
), but it looks like usage of React.memo
has recently made it into the codebase. Does this mean you no longer support React < 16.6? Apologies if this has been called out somewhere, but I couldn’t find it in the migration guide or changelog.
Issue Analytics
- State:
- Created 4 years ago
- Comments:9 (8 by maintainers)
Top Results From Across the Web
Error with 5.1.0-beta and React < 16.6 · Issue #6764 - GitHub
Describe the bug When using React < 16.6, storybook 5.1.0-beta fails to load in the browser with the following error in the dev...
Read more >React does not recognize my file to connect to firebase. What ...
My application gives an error to connect to Firebase. What is the solution of this? I couldn't find out what the configuration error...
Read more >React Hook Form - Set Error / Clear Error - CodeSandbox
VS Code's tsserver was deleted by another application such as a misbehaving virus detection tool. Please reinstall VS Code. Manage Extension.
Read more >React v16.6.0: lazy, memo and contextType
We're adding another error method that lets you render the fallback UI before the render completes. See the docs for getDerivedStateFromError() ...
Read more >Releases - styled-components
Fix React Native components accepts function as style prop. (see #3389) ... 5.0.0-beta.7 was unpublished due to a build error ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Gadzooks!! I just released https://github.com/storybooks/storybook/releases/tag/v5.1.0-rc.0 containing PR #6818 that references this issue. Upgrade today to try it out!
Because it’s a pre-release you can find it on the
@next
NPM tag.Closing this issue. Please re-open if you think there’s still more to do.
I encountered the same issue (workaround: downgrade to
5.1.0-alpha.39
).