-
-
Notifications
You must be signed in to change notification settings - Fork 43
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
Add React Native support #80
Comments
I'm curious how this will look, because we are using React Native (Web) and currently have 2 different packages, one for React Native and one for WebComponents. We already share a lot of code, but when we can develop React Native components directly with Atomico, this would be amazing 😃 |
Excellent!, from [email protected] we can replace the virtualDOM render according to the environment, this allows us:
replace tags with a dictionary of React native's own tagsI have pending work on 2 tasks:
Since it's an exclusive integration for React, it should work like this: import { wrapper } from "@atomico/react-native";
import { MyComponent } from "./my-component";
export const ReactNativeMyComponent = wrapper(MyComponent ); For now that's the goal 🤓 |
Okay! I really wanna help out with this, to make it possible.
Next question would be: What about Animations with the I think all that is not so easy as it sounds, because I'm working with React Native since about 6 years now, and we also are using React Native Web for developing Design Systems here at IBM iX. Of course it would be interesting then when we have React Native support, also add support for React Native Web to bring everything back to Web 🤯 EDIT: FYI, we use React Native styles (a package containing all React Native styles as simple objects) and convert them using stylis and then use them with Atomico |
Amazing (Sorry for the delay in my response), I'm going to centralize this in a repo, so we can work on this together |
Through the strategy already used in atomico/ssr it is possible to support React Native.
The text was updated successfully, but these errors were encountered: