-
-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Installation Confusion RN-.44 #1228
Comments
@smooJitter make sure you are running |
So both @storybook/cli and getstorybook should be setup on -g then under my project root, I should I should also run getstorybook -g: myAwesomeProject: That's it? No need to run npm i @storybook/react-native locally?
|
you can do it globally or locally. doing it locally is a bit safer and will work even if you have an old version of getstorybook installed globally:
|
Thanks, I see. There are two sets of instructions . In one case, getstorybook is encouraged, in another npm i @storybook/react-native. Now that the installation works, the example (react-native-vanilla) repo does not reveal any stories.
/storybook/stories
Although I am not calling it directly, I do see and index.ios.js file /storybook
I have a welcome screen but no stories appear in the left sidebar. |
Did you also run the app in the simulator? Stories won't show up unless (1) storybook is running in the browser, and (2) your app is running in the simulator and has connected to storybook. |
Still no luck. Totally clean RN install, no add package and just the RN welcome screen. No components appear. |
@smooJitter If you create a public repo I can take a look for you. |
I have the exact same problem. The storybook doesn't show any stories. I am running RN 0.45.1 on a 'react-native init' project. EDIT: I fixed my problem by replacing the variable for the root component name with a string.
|
Thanks @fraherm for posting that. I think it will help some people. Question: here is the code that should set the APP_NAME on your machine:
Any idea why this is failing on your machine? I've opened up a separate bug for this, and would like to improve the heuristic and also print out a big warning if it fails so at least it is less confusing the user can do something about it by hand: #1277 |
FYI @fraherm @smooJitter I have fixed the bug in #1277 and it went out in the 3.1.4 release https://github.com/storybooks/storybook/releases/tag/v3.1.4 @smooJitter please let me know if this helps you out |
Looks like it's been fixed. Please reopen this if there's still a problem on the latest versions. |
So how exactly does one go about installing this package?
npm install @storybook/react-native
or cd into project and run
getstorybook.
The documentation (depending on where you look) is not very clear. In any case, getstorybook creates files pointing to @kadira-storybook. Furthermore, will yarn work? This package killed my _dev project and I spent all day trying to repair it.
react-native .44
The text was updated successfully, but these errors were encountered: