An in-range update of react is breaking the build 🚨

## There have been updates to the *react* monorepoundefined

🚨 [View failing branch](https://github.com/DECODEproject/zenroom-studio/compare/master...DECODEproject:greenkeeper%2Fmonorepo.react-16.5.2).

This version is **covered** by your **current version range** and after updating it in your project **the build failed**.

This monorepo update includes releases of one or more dependencies which all belong to the [react group definition](https://github.com/greenkeeperio/monorepo-definitions).

react is a devDependency of this project. It **might not break your production code or affect downstream projects**, but probably breaks your build or test tools, which may **prevent deploying or publishing**.

Status Details

- ✅ **continuous-integration/travis-ci/push:** The Travis CI build passed ([Details](https://travis-ci.org/DECODEproject/zenroom-studio/builds/430305184?utm_source=github_status&utm_medium=notification)).
- ❌ **continuous-integration/appveyor/branch:** AppVeyor build failed ([Details](https://ci.appveyor.com/project/puria/zenroom-studio-02nrq/build/329)).

---

Release Notes for v16.5.2

React DOM

• Fixed a recent <iframe> regression (@JSteunou in #13650)


• Fix updateWrapper so that <textarea>s no longer re-render when data is unchanged (@joelbarbosa in #13643

Schedule (Experimental)

• Renaming "tracking" API to "tracing" (@bvaughn in #13641)


• Add UMD production+profiling entry points (@bvaughn in #13642)


• Refactored schedule to remove some React-isms and improve performance for when deferred updates time out (@acdlite in #13582)

FAQ and help

There is a collection of [frequently asked questions](https://greenkeeper.io/faq.html). If those don’t help, you can always [ask the humans behind Greenkeeper](https://github.com/greenkeeperio/greenkeeper/issues/new).

---

Your [Greenkeeper](https://greenkeeper.io) Bot :palm_tree:

Start by comparing the Greenkeeper failing branch with master and inspect the failed AppVeyor build; the payload does not identify a source file or test. Determine which React update causes the build failure, then verify that the relevant build and test checks pass with the dependency update.

Written by the indexing model from the issue text.