search

appbaseio / reactivesearch

Search UI components for React and Vue
https://opensource.appbase.io/reactivesearch
Apache License 2.0
4.89k stars 471 forks source link

Running reactivesearch-native without expo #405

Open Kisepro opened 6 years ago

Kisepro commented 6 years ago

Hello,

Is it possible to run reactivesearch-native without Expo ? If it isn't, Is it planned ?

For the moment I get the error : image

metagrover commented 6 years ago

Hi @Kisepro, we use react-native-maps exposed by expo for the ReactiveMap component - for usability reasons. It is much easier to set up the map component that way. If you just install expo as your dependency here (as it is a peer dependency for reactivesearch-native now), things should start working. It won't affect your project setup in any way.

So, run:

yarn add expo

Let me know if that doesn't work. I will be happy to help you through this 🐱

Kisepro commented 6 years ago

Hey @metagrover ,

Thanks for your answer.

I tried it and it's unfortunately not as easy. After have installed the expo package, it asks to use the expokit, what I tried too but then I get anothers errors,... I guess the concept is to not have to use the ExpoKit to stay detached

Error I get after installed expo AND added the import line "import { ReactiveBase } from '@appbaseio/reactivesearch-native';" :

image

metagrover commented 6 years ago

Oh okay. I will try it in a fresh setup and get back to you soon on this.

nathan-rumbleon commented 6 years ago

Is there any workaround for this without having to manually remove the expo dependencies from the node modules folder? I can't build my app anymore from AppCenter :(

metagrover commented 6 years ago

Thank you for the patience on this guys. I tried out the latest release on a fresh (non-expo) setup and it was non-functional. There were series of errors that will take some more time at my end for figuring out the next steps.

As I've mentioned here before that we use react-native-maps exposed by expo for the ReactiveMap component - which is causing the issue here. So most probably, we will release the native maps library as a separate package (until we find a valid approach to deal with this issue). The maps package, will then require expo based projects to run on.

For now, you can downgrade reactivesearch-native to 0.7.1 and things should work smoothly.

I will make sure that we do another release in the coming week with this segregation and some other important overall enhancements.