question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error with 5.1.0-beta and React < 16.6

See original GitHub issue

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 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:closed
  • Created 4 years ago
  • Comments:9 (8 by maintainers)

github_iconTop GitHub Comments

1reaction
shilmancommented, May 21, 2019

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.

1reaction
kaeligcommented, May 15, 2019

I encountered the same issue (workaround: downgrade to 5.1.0-alpha.39).

Read more comments on GitHub >

github_iconTop 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 >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found