(0, _typeof4.default) is not a function
See original GitHub issueUnfortunately even on 3.2.5 I’m still getting the issue from #1665. I’m no longer as strongly convinced that it’s babel config.
Reproduction steps:
- Clone the master branch here: https://github.com/hummingbird-me/kitsu-mobile
- Run
getstorybook - Run
yarn run storybook - Run
react-native run-ios
I’ll keep digging on my side, but unfortunately this isn’t resolved yet. Does anyone have any ideas? I can’t seem to figure out what’s causing it, and running react-native run-ios without Storybook works.
Issue Analytics
- State:
- Created 6 years ago
- Comments:19 (7 by maintainers)
Top Results From Across the Web
Unit test failed: TypeError: (0 , _typeof4.default) is not a function
Hi. It looks like the native typeof isn't used but some function typeof. I don't know if it works the same way as...
Read more >react-test-renderer returns TypeError: (0 , _typeof4.default) is ...
Do you want to request a feature or report a bug? ... react-test-renderer returns TypeError: (0 , _typeof4.default) is not a function #15886....
Read more >Jest failing with TypeError: (0 , _user.default) is not a function
I had this same problem and I solved it doing: jest.mock('../src/services/user', () => ({ __esModule: true, default: () => Promise.resolve({ ...
Read more >typeerror (0 _ typeof4.default) is not a function jest - 掘金
1 . python使用json.jsonify 将结果转为json格式时,爆出如上TypeError: Object of type 'ndarray' is not JSON serializable错误。 @app.index, count = data_analyse ...
Read more >JavaScript: The Good Parts (Book Report)
for (i = 0; i < 10; i += 1) {. <statements>. } ▷ For-in loop for (x in xs) {. // Ensure...
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 Free
Top 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

I’m going to close this issue for now because there’s no real reproduction of this. Maybe the solution is to just remove all
node_modulefiles and delete the lock files and reinstall.If someone has a repro on Github, please comment back and we’ll reopen the issue.
This seems like it’s a caching issue for me as well. I was having this issue and wasn’t getting a good stack trace, so I started dropping console.log()s at
getStorybookUIto find the failing line.As soon as I got to
node_modules/react-inspector/node_modules/babel-runtime/helpers/possibleConstructorReturn.jsit miraculously started working again. Unclear why.