chore(deps): update dependency @welldone-software/why-did-you-render to v8 (!7) · Merge requests · Zandor Smith / react-dates

Renovate requested to merge renovate/welldone-software-why-did-you-render-8.x into master Jun 07, 2024

This MR contains the following updates:

Package	Type	Update	Change
@welldone-software/why-did-you-render	devDependencies	major	`^3.6.0` -> `^8.0.0`

Release Notes

welldone-software/why-did-you-render (@welldone-software/why-did-you-render)

`v8.0.3`: Minor update

Compare Source

Updated all packages, besides eslint (8->9) because it was a pretty big update. I might do it later.
Fix #286 - set defaultProps to undefined when it's not present in the original to not have the warning "Support for defaultProps will be removed from function components in a future major release" by @Hypnosphi. Thank you!
Readme updates by myself @vzaidman and @sergeylaptev. Thank you!

`v8.0.1`

Compare Source

Breaking changes

Now only support React 18 since it differs quite a lot from previous versions when monkey patching. by @vzaidman
- For older versions use @^7
Renamed the internal property that checks if React is monkey patched from React.isWDYR to React.__IS_WDYR__ by @vzaidman

Non-breaking changes

Add support for useSyncExternalStore by @iamakulov in https://github.com/welldone-software/why-did-you-render/pull/283
Updated all packages to latest versions and adjusted tests, builds and dev server
- no more yarn audit vulnerabilities by @vzaidman

oops! please use v8.0.1 and above :)

`v7.0.1`

Compare Source

fixed the reference to React 18 in peerDependencies in package.json. Thank you @jussikinnula!

`v7.0.0`: React 18

Compare Source

Added support to React 18! Thank you @jussikinnula!
Upgraded all packages
Improved race conditions in E2E tests that caused them to fail in the latest Chrome versions
- It also made the tests clearer and faster

`v6.2.3`: maintenance

Compare Source

Update all packages
Fixed tests for new versions
Fixed eslint for new versions
Added some TS types. Thank you @bduff9.
Improved the readme

`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

fixed #196 - added jsx-runtime types (Thank you @hrazmsft)

`v6.1.2`

Compare Source

updated all packages
fixed defaultProps being lost on components patched by wdyr. Thank you @joeyparis!! https://github.com/welldone-software/why-did-you-render/pull/194

`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!!

MR: 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.1`: React 17, Automatic JSX runtime transform

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
  - 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:

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 MR.
Added a full e2e coverage using cypress that runs in the pipelines.
updated all dev packages

`v4.3.1`

Compare Source

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

`v4.3.0`: Improved development

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

small typescript update. thanks @igorrmotta!

`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

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: