Realm is a mobile database: an alternative to SQLite & key-value stores
In case you don't want to use the precompiled version on npm, you can build Realm yourself from source. You’ll need an Internet connection the first time you build in order to download the core library.
Prerequisites: * Xcode 12+ * node.js version 10.19 or later * nvm (on Mac and Linux) * cocoapods (on Mac) * Android SDK 23+ * Android NDK 21.0 - Available via the SDK Manager in Android Studio Tools > SDK Manager. - From the command-line:
$ANDROID_SDK_ROOT/tools/bin/sdkmanager --install "ndk;21.0.6113669". * Android CMake - Available via the SDK Manager in Android Studio Tools > SDK Manager - From the command-line
$ANDROID_SDK_ROOT/tools/bin/sdkmanager --install "cmake;3.18.1"`
Clone RealmJS repository:
git clone https://github.com/realm/realm-js.git cd realm-js git submodule update --init --recursive
Note: On Windows the RealmJS repo should be cloned with symlinks enabled ```
git clone -c core.symlinks=true https://github.com/realm/realm-js ```
or manually create the symlinks using directory junctions if you already have the repo cloned. ```
del src del vendor mklink /j "src" "../../../../../src/" mklink /j "vendor" "../../../../../vendor" cd realm-js\tests\react-test-app\android\app\src\main
del assets mklink /j assets "../../../../../data" ```
Note: If you have cloned the repo previously make sure you remove your node_modules directory since it may contain stale dependencies which may cause the build to fail.
⌘ + B
export ANDROID_NDK_HOME=$ANDROID_HOME/ndk/21.0.6113669 #Location for your NDK folder
Be sure you have python2.7 as the default python. 3.x won't work, and it's not enough to use
--python=python2.7as parameter to npm. For example you can use Homebrew to install it.
brew install [email protected]
npm install --build-from-source=realm
On Windows you will need to setup the environment for node-gyp:
Option 1: Install windows-build-tools node package
# run in elevated command prompt (as Administrator) npm install -g --production windows-build-tools
Option 2: Manually install and configure as described in the node-gyp manual.
Note you may need to configure the build tools path using npm
npm config set msbuild_path "C:\Program Files (x86)\Microsoft Visual Studio\2019\Community\MSBuild\Current\Bin\MSBuild.exe"
You also need to install openssl libraries with vcpkg:
git clone https://github.com/Microsoft/vcpkg cd vcpkg bootstrap-vcpkg.bat vcpkg install openssl:x64-windows-static mkdir C:\src\vcpkg\installed\x64-windows-static\lib copy .\packages\openssl-windows_x64-windows-static\lib\libeay32.lib C:\src\vcpkg\installed\x64-windows-static\lib\ copy .\packages\openssl-windows_x64-windows-static\lib\ssleay32.lib C:\src\vcpkg\installed\x64-windows-static\lib
We've decided to slowly migrate this repository to a mono-repository containing multiple packages (stored in the
./packagesdirectory), to install & link these, run
npx lerna bootstrap
Please familiarise yourself with Lerna to learn how to add dependencies to these packages.
API documentation is written using JSDoc.
npm run jsdoc
The generated docs can be found by opening
You can use Visual Studio Code to develop and debug. In the
.vscodefolder, configuration for building and debugging has been added for your convience.
To begin, you will need to build the node addon and prepare the test environment:
npm install --build-from-source --debug (cd tests && npm install)
Prior to begin debugging, you must start Realm Object Server. In VSCode, under menu Tasks/Run Task, find Download and Start Server.
In the debugging pane, you can find
Debug LLDB + NodeJSin the dropdown. First select Start Debugging in the Debug menu.
Some users have reported the Chrome debugging being too slow to use after integrating Realm into their react-native project. This is due to the blocking nature of the RPC calls made through the Realm library. See https://github.com/realm/realm-js/issues/491 for more information. The best workaround is to use Safari instead, as a user has described here.
The tests will spawn a new shell when running, so you need to make sure that new shell instances use the correct version of
npm. On Mac you can use Homebrew and you can add the following to your preferred shell setup:
export NVM_DIR="$HOME/.nvm" . "$(brew --prefix nvm)/nvm.sh"
sudo gem install cocoapods
You can now use
scripts/test.shto run the various tests. You will need yarn installed on the machine.
If you modify or add a test, please remove
test.sh(of course, only if you are testing with React Native).
On Windows some of these targets are available as npm commands.
npm run eslint npm run node-tests npm run test-runners
You can attach a debugger to react-native tests by passing "Debug" to the
test.shscript. A Chrome browser will open and connect to the react native application. Use the built-in Chrome Debugger to debug the code.
./scripts/tests.sh react-tests Debug
Using Visual Studio Code
You can debug node tests using Visual Studio Code. Just use one of the launch configurations.
Asynchronously submits install information to Realm.
Why are we doing this? In short, because it helps us build a better product for you. None of the data personally identifies you, your employer or your app, but it will help us understand what language you use, what Node.js versions you target, etc. Having this info will help prioritizing our time, adding new features and deprecating old features. Collecting an anonymized application path & anonymized machine identifier is the only way for us to count actual usage of the other metrics accurately. If we don’t have a way to deduplicate the info reported, it will be useless, as a single developer
npm install-ing the same app 10 times would report 10 times more than another developer that only installs once, making the data all but useless. No one likes sharing data unless it’s necessary, we get it, and we’ve debated adding this for a long long time. If you truly, absolutely feel compelled to not send this data back to Realm, then you can set an env variable named
Currently the following information is reported:
## Known issues
See CONTRIBUTING.md for more details!
Realm JS and Realm Core are published under the Apache License 2.0.
This product is not being made available to any person located in Cuba, Iran, North Korea, Sudan, Syria or the Crimea region, or to any other person that is not eligible to receive the product under U.S. law.
If you use Realm and are happy with it, all we ask is that you please consider sending out a tweet mentioning @realm to share your thoughts
And if you don't like it, please let us know what you would like improved, so we can fix it!