Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with @depfu rebase.
All Depfu comment commands
@depfu rebase
Rebases against your default branch and redoes this update
@depfu recreate
Recreates this PR, overwriting any edits that you've made to it
@depfu merge
Merges this PR once your tests are passing and conflicts are resolved
@depfu close
Closes this PR and deletes the branch
@depfu reopen
Restores the branch and reopens this PR (if it's closed)
@depfu pause
Ignores all future updates for this dependency and closes this PR
@depfu pause [minor|major]
Ignores all future minor/major updates for this dependency and closes this PR
@depfu resume
Future versions of this dependency will create PRs again (leaves this PR as is)
Here is everything you need to know about this upgrade. Please take a good look at what changed and the test results before merging this pull request.
What changed?
✳️ @welldone-software/why-did-you-render (^4.0.0 → ^5.0.0) · Repo
Release Notes
5.0.0
Does any of this look wrong? Please let us know.
Commits
See the full diff on Github. The new version differs by 22 commits:
v5.0.0
Merge pull request #137 from welldone-software/version_5
updated all packages
updated readme with clarification about React 17
build all branches
v5.0.0-rc.1
upgraded all dev dependencies
instead of logging useMemo and useCallback, log children rendered by them if their deps are deep equal
v5.0.0-alpha.4
updated all packages
v5.0.0-alpha.3
v5.0.0-alpha.2
Consider useCallback result different unless the dependencies are absent or deep equal
updated readme with a few words about sourcemaps
v5.0.0-alpha.1
removed adding dist to git
added a detailed diff report
fixed e2e tests expectations for the new default "ownLoggedReasons: true"
removed exposing the librarie's src
updated all packages
version 5 updates:
remove dist from source control
Depfu will automatically keep this PR conflict-free, as long as you don't add any commits to this branch yourself. You can also trigger a rebase manually by commenting with
@depfu rebase
.All Depfu comment commands