I noticed that Realm JS had fixes that didn't make it into a release of Studio. I suggest we setup some sort of CI that creates a PR upgrading Realm JS on this project whenever a new version of Realm JS becomes available:

• [ ] Create a mechanism of getting notificed by new versions of Realm JS, as a downstream job on Jenkins or perhaps a daily polling of npm show realm versions.
• [ ] Change the dependency on Realm JS to be anything with major version 2 (^2.0.0 or 2.x.x).
• [ ] Automate pushing a branch to this repo with changes to the package-lock.json: Essentially running npm update realm and committing the changes.
• [ ] Automate creating a PR from the branch.

For information about the NPM package lock and why this is needed - please read https://docs.npmjs.com/files/package-locks