-
-
Notifications
You must be signed in to change notification settings - Fork 114
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
[Question] Expo compatibility #207
Comments
@fobos531 give it a try with an expo project: install from master:
then run |
Thank you for the prompt response! I'm currently a bit busy with real-life stuff but I'll try it as soon as possible |
Hello @ammarahm-ed , we tried in our project and seems working fine, thank you for your work! |
@Wyctus i think the version on npm already published. The master branch is for next release. |
@ammarahm-ed |
@Wyctus I have updated the docs. |
Thank you very much! |
Hello - first of all, thanks for the awesome library, I'm using it in multiple projects and it's always worked very reliably for me. I scoured the repo for information on Expo support and noticed that it's suggested to eject from Expo to use this library. While this makes perfect sense, with the advent of Expo dev clients and Expo config plugins, it's been increasingly possible to use previously-incompatible libraries with Expo managed workflow. Is that something you think this project and the ecosystem would benefit from? A similar library - react-native-mmkv - has implemented a way to automate the setup of the library in a way that it makes it compatible with Expo - see mrousavy/react-native-mmkv@d0c6f01
Is that something that would possible here as well?
Thanks in advance!
The text was updated successfully, but these errors were encountered: