-
Notifications
You must be signed in to change notification settings - Fork 368
Error when used with React Native. StoreType= Memory #151
Comments
I am not familiar with React, but the problem seems to be coming from the 1st line in lovefield.min.js, see https://github.com/google/lovefield/blob/master/dist/lovefield.min.js#L1. I suggest exploring a bit what makes it blow up (maybe comment out the 1st and last line of lovefield.min.js and retry). As explained at https://github.com/google/lovefield/blob/master/docs/FAQ.md#can-lovefield-be-used-with-angularbootstrapcordovad3-, we can't possibly ensure that Lovefield works with all JS frameworks, but we will consider a PR/suggestion. |
The clean up is needed for detecting self in a better way. self is not a standard thing. |
I have configured lovefield properly with React + WebPack. Soon I will post some details how but basically:
And later if you use webpack, you can import it like this: const db = require('imports?this=>window!exports?ahoydb&lf!./ahoydb') Where |
@freshp86 You don't have to play with react and others.
or
I am using tools/node_bootstrap to include lovefield in my react native app. For persistance I am using data type React Native developers prefer Realm.io but I chose lovefield as its really fast compared to Realm.io |
@veenedu currently directly use node_bootstrap in RN throw errors, can you share more about how you made it work |
I am planning to use it with react native, as in Memory dataEngine.
I am getting error just in importing the file in both android and iOs. Platforms.
import lf from 'lovefield'
this is the only line of code I have written.
The text was updated successfully, but these errors were encountered: