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.

Uncaught TypeError: Object(...) is not a function - @emotion

See original GitHub issue

Describe the bug When updating @storybook/react to 4.0.7, we are receiving the following error:

To Reproduce Steps to reproduce the behavior:

Go to https://github.com/IBM/carbon-charts
Update @storybook/react version in packages/react/package.json to 4.0.7
Run npm install on the root folder of the repo
Run npm run storybook in packages/react

Issue Analytics

State:
Created 5 years ago
Reactions:18
Comments:45 (11 by maintainers)

Top GitHub Comments

9reactions

magicsponcommented, Nov 28, 2018

I’m seeing this issue.

Using react 16.6.3, @storybook/react 4.0.9 and @emotion/core 10.0.0

cheers

8reactions

shilmancommented, Jan 10, 2019

Support for Emotion 10 is part of Storybook 5.0, which hasn’t reached alpha yet. I’ll post here when it’s ready to try out – ETA next week.

Top Results From Across the Web

Emotion - imported into project and getting errors TypeError ...

Similar to Runtime error 'Object(...) is not a function' when consuming component package leveraging emotion/react.

Uncaught TypeError: Object(...) is not a function - @emotion

1. Go to https://github.com/IBM/carbon-charts · 2. Update @storybook/react version in packages/react/package.json to 4.0.7 · 3. Run npm install on ...

uncaught typeerror: (0 , react__ ...

When trying to edit a record I get the Error "navigator.block is not a function". Steps to reproduce: 1- User the Form Component...

@emotion/cache - npm

@emotion/cache. TypeScript icon, indicating that this package has built-in type declarations · Keywords.

Understanding the "Objects are not valid as a react child" Error ...

Although the error doesn't make it very clear what mistake was made, it states a clear rule: You can't use JavaScript Objects as...