status-im/realm-js
2
0
Fork 0
mirror of https://github.com/status-im/realm-js.git synced 2025-01-09 05:52:24 +00:00
Code Issues Projects Releases Wiki Activity
realm-js/lib/.eslintrc

11 lines
118 B
Plaintext
Raw Normal View History

Initial concept of JS for Chrome debugging The idea is that we will have an NPM module that should always be required to use the Realm JS API. It will handle the underlying implementation details depending on which environment it is being run in (i.e. JavaScriptCore, Chrome, Node). The focus here was on stubbing out the machinery required to get React Native Chrome debugging working with the Realm API by leveraging synchronous requests. The app itself will need to run a web server that responds to these requests.
2015-10-01 22:56:47 -07:00
{
"env": {
"commonjs": true,
"browser": true,
"es6": true,
},
Update RPC JS to use originalXMLHttpRequest React Native now leaves the original object accessible when it "polyfills" objects. So we check for that, but still have the previous logic in place in case they change their minds.
2015-10-20 23:59:02 -07:00
"globals": {
"global": true
Initial concept of JS for Chrome debugging The idea is that we will have an NPM module that should always be required to use the Realm JS API. It will handle the underlying implementation details depending on which environment it is being run in (i.e. JavaScriptCore, Chrome, Node). The focus here was on stubbing out the machinery required to get React Native Chrome debugging working with the Realm API by leveraging synchronous requests. The app itself will need to run a web server that responds to these requests.
2015-10-01 22:56:47 -07:00
}
}
Reference in New Issue Copy Permalink