This version is covered by your current version range and after updating it in your project the build went from success to failure.
As react-dom is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right?
Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
React package and browser build no longer "secretly" includes React DOM. (@sebmarkbage in #7164 and #7168)
Required PropTypes now fail with specific messages for null and undefined. (@chenglou in #7291)
Improved development performance by freezing children instead of copying. (@keyanzhang in #7455)
React DOM
Fixed occasional test failures when React DOM is used together with shallow renderer. (@goatslacker in #8097)
Added a warning for invalid aria- attributes. (@jessebeach in #7744)
Added a warning for using autofocus rather than autoFocus. (@hkal in #7694)
Removed an unnecessary warning about polyfilling String.prototype.split. (@nhunzaker in #7629)
Clarified the warning about not calling PropTypes manually. (@jedwards1211 in #7777)
The unstable batchedUpdates API now passes the wrapped function's return value through. (@bgnorlov in #7444)
Fixed a bug with updating text in IE 8. (@mnpenner in #7832)
React Perf
When ReactPerf is started, you can now view the relative time spent in components as a chart in Chrome Timeline. (@gaearon in #7549)
React Test Utils
If you call Simulate.click() on a <input disabled onClick={foo} /> then foo will get called whereas it didn't before. (@nhunzaker in #7642)
React Test Renderer
Due to packaging changes, it no longer crashes when imported together with React DOM in the same file. (@sebmarkbage in #7164 and #7168)
ReactTestRenderer.create() now accepts {createNodeMock: element => mock} as an optional argument so you can mock refs with snapshot testing. (@Aweary in #7649, #8261)
Hello lovely humans,
react-dom just published its new version 15.4.0.
This version is covered by your current version range and after updating it in your project the build went from success to failure.
As react-dom is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.
I recommend you give this issue a high priority. I’m sure you can resolve this :muscle:
Of course this could just be a false positive, caused by a flaky test suite, or third parties that are currently broken or unavailable, but that would be another problem I’d recommend working on.
Do you have any ideas how I could improve these pull requests? Did I report anything you think isn’t right? Are you unsure about how things are supposed to work?
There is a collection of frequently asked questions and while I’m just a bot, there is a group of people who are happy to teach me new things. Let them know.
Good luck with your project :sparkles:
You rock!
:palm_tree:
GitHub Release
React
React DOM
aria-attributes. (@jessebeach in #7744)autofocusrather thanautoFocus. (@hkal in #7694)String.prototype.split. (@nhunzaker in #7629)batchedUpdatesAPI now passes the wrapped function's return value through. (@bgnorlov in #7444)React Perf
React Test Utils
Simulate.click()on a<input disabled onClick={foo} />thenfoowill get called whereas it didn't before. (@nhunzaker in #7642)React Test Renderer
ReactTestRenderer.create()now accepts{createNodeMock: element => mock}as an optional argument so you can mock refs with snapshot testing. (@Aweary in #7649, #8261)This pull request was created by greenkeeper.io.
Tired of seeing this sponsor message? :zap:
greenkeeper upgrade