Development slowed by detaching from expo
Closed this issue · 5 comments
I've removed the native tesseract code. Do I still need to be detatched from expo? It could possibly greatly speed up the development by simplifying the tooling if it weren't.
Right now all I'm depending on that it not in expo is the React-Native-Camera plugin.
Here's a discussion about other people having this exact problem and not wanting to detach just to use the camera plugin. It looks like they may have fixed it by implementing something just like it in expo version 20:
https://expo.canny.io/feature-requests/p/camera-component
It looks like the expo camera component from version 20 does just what I want from the react-native-camera code that's currently keeping me detached from simple expo development.
The only thing is I'm unsure about base64 support. It only seems to output a uri but it may also have the depricated base64 support like in the react-native-camera component. Maybe I just need to do the same trick to get it working.
Also in the react-native-camera repo I saw discussions on how the current best practice way to do that was to use the react native fs instead. Idk why but here's a link to where I was looking into that:
#1 (comment)
expo/expo#108
https://docs.expo.io/versions/latest/sdk/filesystem.html
It looks like they implemented the react native fs in expo version 19. I still don't see any mention of base64 encoding in the expo filesystem docs though.
https://github.com/itinance/react-native-fs
control-f "base64"