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

[greenkeeper]

There have been updates to the react monorepoundefined

🚨 View failing branch.

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.

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 could not complete due to an error (Details).

---

Release Notes for v16.5.1

16.5.1 (September 13, 2018)

React

• Improve the warning when React.forwardRef receives an unexpected number of arguments. (@andresroberto in #13636)

React DOM

• Fix a regression in unstable exports used by React Native Web. (@aweary in #13598)
• Fix a crash when component defines a method called isReactComponent. (@gaearon in #13608)
• Fix a crash in development mode in IE9 when printing a warning. (@link-alex in #13620)
• Provide a better error message when running react-dom/profiling with schedule/tracking. (@bvaughn in #13605)
• If a ForwardRef component defines a displayName, use it in warnings. (@probablyup in #13615)

Schedule (Experimental)

• Add a separate profiling entry point at schedule/tracking-profiling. (@bvaughn in #13605)

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

---

Your Greenkeeper Bot 🌴

[greenkeeper]

After pinning to 16.5.0 your tests are still failing. The reported issue might not affect your project. These imprecisions are caused by inconsistent test results.

[greenkeeper]

• The devDependency react was updated from 16.5.1 to 16.5.2.
• The devDependency react-dom was updated from 16.5.1 to 16.5.2.

Your tests are still failing with these versions. Compare changes

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)

[greenkeeper]

• The devDependency react was updated from 16.5.2 to 16.6.0.
• The devDependency react-dom was updated from 16.5.2 to 16.6.0.

Your tests are still failing with these versions. Compare changes

[greenkeeper]

• The devDependency react was updated from 16.6.0 to 16.6.1.
• The devDependency react-dom was updated from 16.6.0 to 16.6.1.

Your tests are still failing with these versions. Compare changes

Release Notes for v16.6.1

16.6.1 (November 6, 2018)

React DOM

• Fallback should not remount every time a promise resolves. (@acdlite in #14083)
• Fix bug where Suspense keeps showing fallback even after everything finishes loading. (@acdlite in #14083)
• Fix unresolved default props in lifecycle methods of a lazy component. (@gaearon in #14112)
• Fix bug when recovering from an error thrown during complete phase. (@gaearon in #14104)

Scheduler (Experimental)

• Switch from deadline object to shouldYield API. (@acdlite in #14025)

[greenkeeper]

• The devDependency react was updated from 16.6.1 to 16.6.2.
• The devDependency react-dom was updated from 16.6.1 to 16.6.2.

Your tests are still failing with these versions. Compare changes

[greenkeeper]

• The devDependency react was updated from 16.6.2 to 16.6.3.
• The devDependency react-dom was updated from 16.6.2 to 16.6.3.

Your tests are still failing with these versions. Compare changes

[greenkeeper]

• The devDependency react was updated from 16.6.3 to 16.7.0.
• The devDependency react-dom was updated from 16.6.3 to 16.7.0.

Your tests are still failing with these versions. Compare changes

Release Notes for v16.7.0

React DOM

• Fix performance of React.lazy for large numbers of lazily-loaded components. (@acdlite in #14429)
• Clear fields on unmount to avoid memory leaks. (@trueadm in #14276)
• Fix bug with SSR and context when mixing react-dom/server@16.6 and react@<16.6. (@gaearon in #14291)
• Fix a performance regression in profiling mode. (@bvaughn in #14383)

Scheduler (Experimental)

• Post to MessageChannel instead of window. (@acdlite in #14234)
• Reduce serialization overhead. (@developit in #14249)
• Fix fallback to setTimeout in testing environments. (@bvaughn in #14358)
• Add methods for debugging. (@mrkev in #14053)

[greenkeeper]

• The devDependency react was updated from 16.7.0 to 16.8.0.
• The devDependency react-dom was updated from 16.7.0 to 16.8.0.

Your tests are still failing with these versions. Compare changes

[greenkeeper]

• The devDependency react was updated from 16.8.0 to 16.8.1.
• The devDependency react-dom was updated from 16.8.0 to 16.8.1.

Your tests are still failing with these versions. Compare changes

[greenkeeper]

• The devDependency react was updated from 16.8.1 to 16.8.2.
• The devDependency react-dom was updated from 16.8.1 to 16.8.2.

Your tests are still failing with these versions. Compare changes

Release Notes for v16.8.2

16.8.2 (February 14, 2019)

React DOM

• Fix ReactDOM.render being ignored inside useEffect. (@gaearon in #14799)
• Fix a crash when unmounting empty portals. (@gaearon in #14820)
• Fix useImperativeHandle to work correctly when no deps are specified. (@gaearon in #14801)
• Fix crossOrigin attribute to work in SVG image elements. (@aweary in #14832)
• Fix a false positive warning when using Suspense with Hooks. (@gaearon in #14821)

React Test Utils and React Test Renderer

• Include component stack into the act() warning. (@threepointone in #14855)

[greenkeeper]

• The devDependency react was updated from 16.8.2 to 16.8.3.
• The devDependency react-dom was updated from 16.8.2 to 16.8.3.

Your tests are still failing with these versions. Compare changes

[greenkeeper]

• The devDependency react was updated from 16.8.3 to 16.8.4.
• The devDependency react-dom was updated from 16.8.3 to 16.8.4.

Your tests are still failing with these versions. Compare changes

Release Notes for v16.8.4

16.8.4 (March 5, 2019)

React DOM and other renderers

• Fix a bug where DevTools caused a runtime error when inspecting a component that used a useContext hook. (@bvaughn in #14940)

[greenkeeper]

• The devDependency react was updated from 16.8.4 to 16.8.5.
• The devDependency react-dom was updated from 16.8.4 to 16.8.5.

Your tests are still failing with these versions. Compare changes

[greenkeeper]

• The devDependency react was updated from 16.8.5 to 16.8.6.
• The devDependency react-dom was updated from 16.8.5 to 16.8.6.

Your tests are still failing with these versions. Compare changes

Release Notes for v16.8.6

16.8.6 (March 27, 2019)

React DOM

• Fix an incorrect bailout in useReducer(). (@acdlite in #15124)
• Fix iframe warnings in Safari DevTools. (@renanvalentin in #15099)
• Warn if contextType is set to Context.Consumer instead of Context. (@aweary in #14831)
• Warn if contextType is set to invalid values. (@gaearon in #15142)

Artifacts

• react: https://unpkg.com/react@16.8.6/umd/
• react-art: https://unpkg.com/react-art@16.8.6/umd/
• react-dom: https://unpkg.com/react-dom@16.8.6/umd/
• react-is: https://unpkg.com/react-is@16.8.6/umd/
• react-test-renderer: https://unpkg.com/react-test-renderer@16.8.6/umd/
• scheduler: https://unpkg.com/scheduler@0.13.6/umd/