-
-
Notifications
You must be signed in to change notification settings - Fork 9.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug]: error Unable to resolve module storybook/internal/preview-api #28942
Comments
Same for me as well, after upgrading to RN0.74 |
Facing the same issue -
|
I have got similar error not when running storybook but when running unit tests. The error message is:
I've tried different versions, the error seems related to |
Remove
Run command: sb-rn-get-stories It updates |
This also affects I'm still investigating why this happens. Might be something local to us. EDIT: Seems related to
Not familiar enough with StoryBook to know more right now, but likely related to upgrading from Storybook 6 => 7 => 8.1.10 => 8.3.6. |
Looks like we are using a very old version of Jest that doesn't support package.json export rewriting - jestjs/jest#9771 |
All of your storybook package versions should match. You can run |
This is happening for me with:
Even though all versions match @shilman :-(
|
@vonkanehoffen Do you have the If not, please install it. It's a peer dep of all the Storybook packages. @dannyhw do we need to add it as a peer dep of |
@shilman in This just seems like it could be metro configuration issues though, like not having package exports enabled via withStorybook. |
though the original issue was created before rn sb v8 was out so I would think that two different issues are getting mixed up here |
As mentioned previously by @shilman , we've solved this error by adding the |
@cosieLq Can you provide an reproduction of the problem? that would really help to debug. |
I think I fixed this 2 months ago with
|
@dannyhw Users should still have Consider the following package structure:
If the package manager hoists B, then C will be able to find it. But if it doesn't, then even though B is somewhere in So I'd recommend:
This is a breaking change, so probably need to wait for 8.0 |
Ok seems reasonable, will make sure to update it for the next major. |
We're using '@storybook/react' and '@storybook/react-vite', not '@storybook/react-native', so our error is probably different. After we installed 'storybook' in 'package.json', the error is gone. Do you still need a reproduction? |
Ah in that case that would be expected if the storybook package is not installed i think it's not needed |
Describe the bug
cannot run react-native with latests versions
versions used
project was running with this previous following versions but storybook stopped working few month ago since i udpate react-native itself. it stuck on splascreen most of the time
Reproduction link
nolink.com
Reproduction steps
just try to run project
System
Additional context
No response
The text was updated successfully, but these errors were encountered: