We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
If I use a basic native component everything works great. But I'm trying to use storybook with react-native & react-native-web and I always get:
can't find variable: document
Just try to create an story for a react-native-web and run storybook-react-native ... zero-issues when I'm running the same story in storybook-react.
"@storybook/react": "^3.3.12", "@storybook/react-native": "^3.3.12",
The text was updated successfully, but these errors were encountered:
Isn't react native web supposed to run in a browser? You probably need to use @storybook/react for web–targeted components
@storybook/react
Sorry, something went wrong.
React-native-web runs in both environments web and native :)
Their official storybook example uses @storybook/react though:
https://github.com/necolas/react-native-web/blob/0.5.1/website/package.json
"React Native for Web" brings the platform-agnostic Components and APIs of React Native to the Web.
https://github.com/necolas/react-native-web Pretty sure it's not supposed to be for RN or else it wouldn't be calling document
document
No branches or pull requests
Issue details
If I use a basic native component everything works great. But I'm trying to use storybook with react-native & react-native-web and I always get:
Steps to reproduce
Just try to create an story for a react-native-web and run storybook-react-native ... zero-issues when I'm running the same story in storybook-react.
Please specify which version of Storybook and optionally any affected addons that you're running
Screenshots / Screencast / Code Snippets (Optional)
The text was updated successfully, but these errors were encountered: