Maicki Why Did You Update Versions Save

Made sure we don't monkey patch components at all if they are excluded or not included. (#43, #44) thanks @astik

Now using react-fast-compare to make deep comparisons of react props to detect props which are different by reference but equal by value.

We decided to use it to fix the library's performance issues (#30)

Fixed handling of old and new context api in functional components. (#39)

Fixed support of React's 16 snap argument in componentDidUpdate.

Thanks @kyo-ago

Breaking Changes

• Dropped the support of react 14 and 15:

  With the new monkey patch of version 1, tests are not passing on React 14 or 15. We decided to drop the support of those at all and added a readme notification about it.

Added a test to ensure extended class and functional components are not swallowing statics.

We implemented a new monkey patch which was written by @danburzo. Thank you!

This patch allows us to track updates in components with custom componentDidUpdate and on Functional Components. (fixing #10 and #17)

It works by monkey patching React.createElement instead of React.Component and:

• On class components, extending them to new components with componentDidUpdate inheriting from the originals and using the extended version instead of the original one.

let WDYUFunctionalComponent = class extends YourReactComponent {
  render() {
    return ctor(this.props);
  }
  componentDidUpdate(prevProps, prevState) {
    cdu.call(this, prevProps, prevState);
  }
}

• On functional components, wrapping them by a class component with a custom componentDidUpdate and using the wrapper to create the element instead of the functional component.

Braking Changes

We decided to release it as a major release since we expect it might work a little different then usually tracking more components then previously and (i hope not) braking some components because of the wrapping.

• Got the package size
  • from 316 KB, 59.7 KB minified
  • to 13.89 KB, 4.82 KB minified.
  • Thanks for the contribution @tomchentw
• Updated the readme with a sandbox and a simple explanation on fixing redundant renders.
• Updated all packages
• Made builds use node 10