realm-js/lib/index.js

/* Copyright 2015 Realm Inc - All Rights Reserved
 * Proprietary and Confidential
 */

'use strict';

if (typeof Realm != 'undefined') {
    module.exports = Realm;  // eslint-disable-line no-undef
} else {
    module.exports = require('./realm');
}
Add beta licenses to Chrome JS modules 2015-10-28 10:37:17 -07:00			`/* Copyright 2015 Realm Inc - All Rights Reserved`
			`* Proprietary and Confidential`
			`*/`

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			`'use strict';`

			`if (typeof Realm != 'undefined') {`
			`module.exports = Realm; // eslint-disable-line no-undef`
			`} else {`
partial rpc server implemenation 2015-10-06 13:36:56 -06:00			`module.exports = require('./realm');`
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			`}`