Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): bump @welldone-software/why-did-you-render from 4.1.3-alpha.0 to 4.2.6 #218

Conversation

dependabot-preview[bot]
Copy link
Contributor

Bumps @welldone-software/why-did-you-render from 4.1.3-alpha.0 to 4.2.6.

Release notes

Sourced from @welldone-software/why-did-you-render's releases.

v4.2.6

  • Fixed "track owner reasons" for cloned elements. Thanks @Hypnosphi !
  • Updated all dependencies including a security update for lodash

v4.2.5

fixed WDYR trying to track untrackable React elements which resulted in a redundant console error to the console. thanks @MaffooBristol

v4.2.4

fixed handling of hook state change during render. thanks @Hypnosphi!!

v4.2.3

  • minor docs improvements
  • minor inner code efficiency improvements
  • fixed a bug where broken code like React.memo(null) raised a console error regarding WDYR failure.
  • updated all dev dependencies

v4.2.2

fixed a false positive regarding React elements with several children with different props: welldone-software/why-did-you-render#117

v4.2.1

fixed false positive regarding different react elements (based on their props) reported as deep equlas

v4.2.0

I came across situations where a component is re-rendered because a property that holds a huge object deep equals to it's previous version is passed to it (after a request to the API that returns the same result)

this caused my console to almost crash with tracks of every single nested property of it.

so now we would:

  • only report the topmost object as being deepEqulas while ignoring what's inside and how much of it is different / deepEquls.

v4.1.3

fixed a certain error when using with Preact.

Preact is not officially supported by the library but seems to work with it.

Commits

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  • @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
  • @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
  • @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
  • @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
  • @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

  • Update frequency (including time of day and day of week)
  • Pull request limits (per update run and/or open at any time)
  • Out-of-range updates (receive only lockfile updates, if desired)
  • Security updates (receive only security updates, if desired)

Bumps [@welldone-software/why-did-you-render](https://github.com/welldone-software/why-did-you-render) from 4.1.3-alpha.0 to 4.2.6.
- [Release notes](https://github.com/welldone-software/why-did-you-render/releases)
- [Commits](welldone-software/why-did-you-render@v4.1.3-alpha.0...v4.2.6)

Signed-off-by: dependabot-preview[bot] <support@dependabot.com>
@dependabot-preview
Copy link
Contributor Author

Superseded by #221.

@dependabot-preview dependabot-preview bot deleted the dependabot/npm_and_yarn/welldone-software/why-did-you-render-4.2.6 branch August 3, 2020 14:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants