Skip to content

Conversation

@renovate
Copy link

@renovate renovate bot commented Dec 12, 2020

WhiteSource Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
@welldone-software/why-did-you-render 4.0.6 -> 6.2.3 age adoption passing confidence

Release Notes

welldone-software/why-did-you-render

v6.2.3

Compare Source

v6.2.2

Compare Source

v6.2.1

Compare Source

  • Updated all packages
  • Adjusted nollup setup files to work with the latest version
  • Fixed TypeScript types for JSX runtime files. Thank you for pointing this one out @​jafin!

v6.2.0

Compare Source

  • updated all packages
  • #​203 - Add delegate parameter to allow for harvesting additional data from react element- an advanced feature by @​ereddrex. Thank you!

v6.1.4

Compare Source

v6.1.3

Compare Source

v6.1.2

Compare Source

v6.1.1

Compare Source

  • Ignoring object getters because accessing them often errors and/or has side effects (fixing #​184)
  • Updated all packages and improved the vscode development environment

v6.1.0

Compare Source

Now also tracks non-plain objects (like new User()).

Thank you @​barakyosi!!

PR: https://github.com/welldone-software/why-did-you-render/pull/179
CLOSED ISSUE: https://github.com/welldone-software/why-did-you-render/issues/74

v6.0.5

Compare Source

fixed the bug "RangeError: Maximum call stack size exceeded" (#​168) by making sure WDYR is not applied more than once under any circumstances.

v6.0.4

Compare Source

  • updated all packages, including security fixes
  • improved the code quality
    • updated test file imports
    • improved eslint rules
  • updated vscode settings files
    • added jest extension settings
    • added eslint autofix
  • improved the readme

v6.0.3

Compare Source

v6.0.2

Compare Source

v6.0.1

Compare Source

Breaking Changes

  • No longer minimizes the library.
    • The minimization created too many inconveniences.
    • It should only be used in dev, and it's small anyway.

Other Changes

  • Added support to React 17.
  • Added support to the new jsx-runtime transform from babel.
    • By the way, this might be a very useful thing for the library in the future.
  • Added a mechanism to test both React 16 and React 17

v5.0.0

Compare Source

Notice:

  • Support for React@17 is on it's way.

Breaking changes:

  • No longer tracks deep equals results in useMemo.
    • Added tests to children re-rendered as a result of useMemo or useCallback results:
      • logs if the different result got generated because of deep equals deps changes
        image
      • ignores the prop change if deps were different
  • No longer tracks re-renders as a result of useCallback invalidation due to deps changes (fixes #​46)
    • This fix was brought to you by the one and only @​Hypnosphi :)
  • Made logOwnerReasons true by default
  • Only build a minimized UMD version now and won't commit the built files to git anymore
  • Removed babel-plugin-lodash because lodash optimizations better are done by the user of the library
  • Removed building in babel-plugin-transform-classes because we build with a newer babel where it is not needed anymore

Enhancements:

  • Added a feature where upon request you can get a detailed diff between props.
    For example for the following:
    const sameObj = {a: {b: 'c'}}
    ReactDom.render(<Main containerProps={{style: {height: '100%'}, className: 'default-highchart', sameObj}} />, domElement)
    ReactDom.render(<Main containerProps={{style: {height: '100%'}, className: 'default-highchart', sameObj}} />, domElement)
    Since props are equal by value, you will see the following option that allows for the generation of a detailed diff report:
    image

Fixes

  • Only track hooks if they are supported

Readme

  • improved readme in general, including the installation tips

Dev

  • Added Travis pipelines that run lint, test, audit, and e2e tests for each PR.
  • Added a full e2e coverage using cypress that runs in the pipelines.
  • updated all dev packages

v4.3.2

Compare Source

v4.3.1

Compare Source

  • fixed owner reasons bug in strict mode, also added a test
  • updated all dev packages

v4.3.0

Compare Source

  • Updated packages
  • Added E2E tests (Cypress)
  • Added CI (Travis CI)
  • Running Unit tests, Lint, Audit, and E2E tests in CI

v4.2.7

Compare Source

v4.2.6

Compare Source

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

v4.2.5

Compare Source

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

v4.2.4

Compare Source

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

v4.2.3

Compare Source

  • 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

Compare Source

fixed a false positive regarding React elements with several children with different props:
https://github.com/welldone-software/why-did-you-render/issues/117

v4.2.1

Compare Source

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

v4.2.0

Compare Source

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

Compare Source

fixed a certain error when using with Preact.

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

v4.1.2

Compare Source

Improved readme to better explain how to add the library to projects without breaking hot reload

v4.1.1

Compare Source

added logOwnerReasons by @​Hypnosphi.

You can read about it here:
https://github.com/welldone-software/why-did-you-render#logownerreasons

added support to Sets tracking by @​jfrumar-infinitusai

v4.0.8

Compare Source

fixed a minor bug where no tracking was made if the previous value of a hook was falsy

v4.0.7

Compare Source

Thank you very much @​OliverJAsh for pr https://github.com/welldone-software/why-did-you-render/pull/104 <3


Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Enabled.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by WhiteSource Renovate. View repository job log here.

@renovate renovate bot force-pushed the renovate/welldone-software-why-did-you-render-6.x branch from d70790b to 58a2c6b Compare January 6, 2021 21:53
@renovate renovate bot force-pushed the renovate/welldone-software-why-did-you-render-6.x branch from 58a2c6b to 19388ee Compare April 26, 2021 16:44
@renovate renovate bot force-pushed the renovate/welldone-software-why-did-you-render-6.x branch from 19388ee to 3a2e92c Compare June 6, 2021 19:46
@renovate renovate bot force-pushed the renovate/welldone-software-why-did-you-render-6.x branch from 3a2e92c to 45dafe1 Compare June 14, 2021 11:10
@renovate renovate bot force-pushed the renovate/welldone-software-why-did-you-render-6.x branch from 45dafe1 to 87ea43b Compare October 18, 2021 19:53
@renovate renovate bot force-pushed the renovate/welldone-software-why-did-you-render-6.x branch from 87ea43b to 16d97b6 Compare March 7, 2022 15:08
@ptb ptb closed this Mar 20, 2024
@ptb ptb deleted the renovate/welldone-software-why-did-you-render-6.x branch March 20, 2024 19:04
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants