-
Notifications
You must be signed in to change notification settings - Fork 558
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
Can't find variable: RealmType #2
Comments
This should now be fixed with commit 1148ac5 |
this is still occurring if debugging in chrome. |
Debugging in chrome does not work as it is built on v8 rather than javascriptCore. We could add some temporary hacks so that the Realm apis are no-ops when in debugging mode, but getting the apis functional in this mode will be a major endeavor. |
hmmm, that's going to be trouble. that's a key tool in the react native toolbelt. we'd end up not be able to debug at all really because something will always depend on the database somewhere in the flow. there's definitely nothing else in the react native world that i've seen that injects things into the js context. I assume you are doing that and not as a npm_module / bridge to work with cordova and be synchronous. probably be something you'd have to figure out to be successful in this space. make it more an npm module and connect without that injection. |
Enable Sync support in Node.js binding
# This is the 1st commit message: adding ts files # This is the commit message #2: updating to ts 2.3.2 and fixing inheritance for ObjectSchema
Moved sync-request into devDependencies
Something is happening that prevents the injection of the
Realm
andRealmType
globals in to the JS framework when you upgrade react to the current version.You can see the issue in the example app if you change the
package.json
to:The text was updated successfully, but these errors were encountered: