Error: You gave us a visitor for the node type StaticBlock but it's not a valid type #12893
Comments
shilman
added
react
cra
|
The following fixes it for me: I think there's a babel version inconsistency between CRA@4 and Storybook@6, but I'm not sure what's the proper fix. |
|
NOTE: this is hopefully fixed in 6.1 ☝️ . We need to get it back into the stable release, but are having problems with repros in CI. In the meantime if people can upgrade to 6.1 to test it out, please give it a try and report back: If it doesn't work right away, try removing regenerating lockfiles. |
|
I'm getting the same problem. But for me I started to see |
|
Seeing this reliably when upgrading from 6.1.0-alpha.22 to 6.1.1 — regenerating the lockfile doesn’t help. We’re not using CRA, but we are using babel for building our code outside of Storybook. I’ll update if I find a specific Babel version/config that fixes the issue. |
|
Removing Rebuilding my yarn.lock was not enough. Here's why:
I think it's safe to mark this closed. |
|
Great detective work @koop. Thanks so much, closing! |
|
Same here, just Run from the app directory: |
worked for me without removing |
|
My error is
but none of the indications worked for me :( |
Getting this same issue on a new expo typescript project |
|
@tjweihra what's the version of your react-scripts package? I updated mine to 5.0.1 and it solved. But now I have a new error:
|
|
@lucasfelixc I just found the issue, my global npm version for expo-cli was 4.x.x, after upgrading i'm now on version 5.4.6. It seems to have fixed my issue, apologies if that doesn't help. |
|
node_modules@react-navigation\native\src\index.tsx: [BABEL] E:\development\zionet\react-native\expo-cli\flights\node_modules@react-navigation\native\src\index.tsx: You gave us a visitor for the node type TSInstantiationExpression but it's not a valid type this is my error today, 2 days ago all worked fine while opened projects... |
update the global expo looks like it work, tnx a lot! |
|
I got : Still don't get what is the problem. I try to update the react-scripts to "5.0.0" |
I've received the same error during global update of project packages. It means You should estimate large amount of time for any project packages update. For my case: I should find an ideal balance between 6800 package dependecies (including parts of babel). |
|
I started getting the same error today (worked fine yesterday): In my case, I use babel programmatically to compile typescript. I don't use Edit: many babel packages were updated to 7.18.0 yesterday. One of the merged PRs is Add support for instantiation expressions , it might be related. |
|
2 days ago was working, now babel broke the internet. I just wasted a day and still unresolved. I'm getting the error in a Next.js project using (expo) & babel. I updated Expo-cli to 5.4.6 and all that is suggested above, no solution. Any solution even temporary? |
|
Forcing @babel/core and @babel/types back to version 7.17 fixed the issue for me, although it feels hacky... Add the resolutions to package.json: Then |
and others
Cannot run storybook in a vanilla create-react-app. It appears to install correctly, but fails on
npm run storybookTo Reproduce
cd /tmp && npx create-react-app storytest && cd storytest && npx sb init && npm run storybookExpected behavior
Storybook is running
Code snippets
Full log:
System
Additional context
None
The text was updated successfully, but these errors were encountered: