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

[greenkeeper]

There have been updates to the react monorepo:

• • 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.
• The devDependency react-test-renderer was updated from 16.5.2 to 16.6.0.

🚨 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 failed (Details).

---

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.2 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.6.0 to 16.6.1.
• The devDependency react-dom was updated from 16.6.0 to 16.6.1.
• The devDependency react-test-renderer 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.
• The devDependency react-test-renderer 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.
• The devDependency react-test-renderer 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.
• The devDependency react-test-renderer 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/[email protected] 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.
• The devDependency react-test-renderer 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.
• The devDependency react-test-renderer 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.
• The devDependency react-test-renderer 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.
• The devDependency react-test-renderer 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.
• The devDependency react-test-renderer 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.
• The devDependency react-test-renderer 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.
• The devDependency react-test-renderer 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/[email protected]/umd/
• react-art: https://unpkg.com/[email protected]/umd/
• react-dom: https://unpkg.com/[email protected]/umd/
• react-is: https://unpkg.com/[email protected]/umd/
• react-test-renderer: https://unpkg.com/[email protected]/umd/
• scheduler: https://unpkg.com/[email protected]/umd/

[greenkeeper]

• The devDependency react was updated from 16.8.6 to 16.9.0.
• The devDependency react-dom was updated from 16.8.6 to 16.9.0.
• The devDependency react-test-renderer was updated from 16.8.6 to 16.9.0.

Your tests are still failing with these versions. Compare changes

Release Notes for 16.9.0 (August 8, 2019)

React

• Add <React.Profiler> API for gathering performance measurements programmatically. (@bvaughn in #15172)
• Remove unstable_ConcurrentMode in favor of unstable_createRoot. (@acdlite in #15532)

React DOM

• Deprecate old names for the UNSAFE_* lifecycle methods. (@bvaughn in #15186 and @threepointone in #16103)
• Deprecate javascript: URLs as a common attack surface. (@sebmarkbage in #15047)
• Deprecate uncommon "module pattern" (factory) components. (@sebmarkbage in #15145)
• Add support for the disablePictureInPicture attribute on <video>. (@eek in #15334)
• Add support for onLoad event for <embed>. (@cherniavskii in #15614)
• Add support for editing useState state from DevTools. (@bvaughn in #14906)
• Add support for toggling Suspense from DevTools. (@gaearon in #15232)
• Warn when setState is called from useEffect, creating a loop. (@gaearon in #15180)
• Fix a memory leak. (@paulshen in #16115)
• Fix a crash inside findDOMNode for components wrapped in <Suspense>. (@acdlite in #15312)
• Fix pending effects from being flushed too late. (@acdlite in #15650)
• Fix incorrect argument order in a warning message. (@brickspert in #15345)
• Fix hiding Suspense fallback nodes when there is an !important style. (@acdlite in #15861 and #15882)
• Slightly improve hydration performance. (@bmeurer in #15998)

React DOM Server

• Fix incorrect output for camelCase custom CSS property names. (@bedakb in #16167)

React Test Utilities and Test Renderer

• Add act(async () => ...) for testing asynchronous state updates. (@threepointone in #14853)
• Add support for nesting act from different renderers. (@threepointone in #16039 and #16042)
• Warn in Strict Mode if effects are scheduled outside an act() call. (@threepointone in #15763 and #16041)
• Warn when using act from the wrong renderer. (@threepointone in #15756)

Artifacts

• react: https://unpkg.com/[email protected]/umd/
• react-art: https://unpkg.com/[email protected]/umd/
• react-dom: https://unpkg.com/[email protected]/umd/
• react-is: https://unpkg.com/[email protected]/umd/
• react-test-renderer: https://unpkg.com/[email protected]/umd/
• scheduler: https://unpkg.com/[email protected]/umd/

[greenkeeper]

• The devDependency react was updated from 16.9.0 to 16.10.0.
• The devDependency react-dom was updated from 16.9.0 to 16.10.0.
• The devDependency react-test-renderer was updated from 16.9.0 to 16.10.0.

Your tests are still failing with these versions. Compare changes

[greenkeeper]

• The devDependency react was updated from 16.10.0 to 16.10.1.
• The devDependency react-dom was updated from 16.10.0 to 16.10.1.
• The devDependency react-test-renderer was updated from 16.10.0 to 16.10.1.

Your tests are still failing with these versions. Compare changes

Release Notes for 16.10.1 (September 28, 2019)

React DOM

• Fix regression in Next.js apps by allowing Suspense mismatch during hydration to silently proceed (@sebmarkbage in #16943)

[greenkeeper]

• The devDependency react was updated from 16.10.1 to 16.10.2.
• The devDependency react-dom was updated from 16.10.1 to 16.10.2.
• The devDependency react-test-renderer was updated from 16.10.1 to 16.10.2.

Your tests are still failing with these versions. Compare changes

Release Notes for 16.10.2 (October 3, 2019)

React DOM

• Fix regression in react-native-web by restoring order of arguments in event plugin extractors (@necolas in #16978)

Artifacts

• react: https://unpkg.com/[email protected]/umd/
• react-art: https://unpkg.com/[email protected]/umd/
• react-dom: https://unpkg.com/[email protected]/umd/
• react-is: https://unpkg.com/[email protected]/umd/
• react-test-renderer: https://unpkg.com/[email protected]/umd/
• scheduler: https://unpkg.com/[email protected]/umd/

[greenkeeper]

• The devDependency react was updated from 16.10.2 to 16.11.0.
• The devDependency react-dom was updated from 16.10.2 to 16.11.0.
• The devDependency react-test-renderer was updated from 16.10.2 to 16.11.0.

Your tests are still failing with these versions. Compare changes

Release Notes for 16.11.0 (October 22, 2019)

React DOM

• Fix mouseenter handlers from firing twice inside nested React containers. @yuanoook in #16928
• Remove unstable_createRoot and unstable_createSyncRoot experimental APIs. (These are available in the Experimental channel as createRoot and createSyncRoot.) (@acdlite in #17088)

Artifacts

• react: https://unpkg.com/[email protected]/umd/
• react-art: https://unpkg.com/[email protected]/umd/
• react-dom: https://unpkg.com/[email protected]/umd/
• react-is: https://unpkg.com/[email protected]/umd/
• react-test-renderer: https://unpkg.com/[email protected]/umd/
• scheduler: https://unpkg.com/[email protected]/umd/

[greenkeeper]

• The devDependency react was updated from 16.11.0 to 16.12.0.
• The devDependency react-dom was updated from 16.11.0 to 16.12.0.
• The devDependency react-test-renderer was updated from 16.11.0 to 16.12.0.

Your tests are still failing with these versions. Compare changes