why-did-you-render

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

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

• improved readme
• updated to react 16.13.1 and tested
• updated all libraries like babel

• improved readme
• improved typescript support
• updated all dev packages and tested the library with them

no breaking changes.

Here is an article about the release

• added typescript definition of whyDidYouRender to pure components
• added typescript definition of trackExtraHooks to initialization options
• updated all packages

• updated packages

• fixed minor bugs and edge cases

• improved readme

• added support to tracking custom hooks:

If a hook returns new states when called, you can make sure WDYR checks that it doesnt recalculates a new "deep equals" object:

whyDidYouRender(React, {trackExtraHooks: [
  [Redux, 'useSelector']
]});

and then

Component.whyDidYouRender = true;

Fixed "module" not being defined in certain cases (#72)

fixed a small edge case (#66) where memo is used on a string like this:

const Svg = React.memo("svg");
Svg.whyDidYouRender = true;

https://codesandbox.io/s/welldone-softwarewhy-did-you-render-memo-a-text-example-pzn3b

• Improved Typescript Types #64 (Thanks @Genhain)
• Updated Dev Packages

fixes #59

• fixed #50 - Doesn't work with class components wrapped in React.memo
• also improved tests
• refactored the code- abstracted some repeated code
• updated packages, including dev packages with security issues

• made sure no unexpected console warns arise when using styled-components or in some forward ref scenarios