leecade / leecade/react-native-unlock
An in-range update of react-addons-test-utils is breaking the build 🚨
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 4
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Version 15.4.0 of react-addons-test-utils just got published.
| Branch | Build failing 🚨 |
|---|---|
| Dependency | react-addons-test-utils |
| Current Version | 15.3.2 |
| Type | devDependency |
This version is covered by your current version range and after updating it in your project the build failed.
As react-addons-test-utils 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 💪
Status Details
Release Notes
v15.4.0React
- 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
autofocusrather thanautoFocus. (@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
batchedUpdatesAPI 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} />thenfoowill 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)
Not sure how things should work exactly?
There is a collection of frequently asked questions and of course you may always ask my humans.
Your Greenkeeper Bot 🌴
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by inspecting the failed CircleCI run linked from the issue for the greenkeeper/react-addons-test-utils-15.4.0 branch, then compare it with the current dependency state. Done means resolving the build failure caused by the 15.4.0 update and confirming that the project checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, react
- Domain
- build-system, testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100