fix(build): Fixed the build.

Eslint config broke the build again. Argh.

feat(react-sizeme): Exposes new configuration option for react-sizeme.

The react-sizeme library now allows a refreshMode configuration option to be provided. This is now

exposed via the component queries configuration.

fix(build): Fixed the build.

Eslint config broke the build again. Argh.

feat(react-sizeme): Exposes new configuration option for react-sizeme.

The react-sizeme library now allows a refreshMode configuration option to be provided. This is now

exposed via the component queries configuration.

fix(component): A static WrappedComponent prop has been added to the …

…HOC to aid testing. Additional

A static WrappedComponent prop has been added to the HOC to aid testing.  Additionally the

"conflictResolver" has been "moved" to the new "config" prop.  The old parameter pass through method

still works but can be considered deprecated.

fix(component): A static WrappedComponent prop has been added to the …

…HOC to aid testing. Additional

A static WrappedComponent prop has been added to the HOC to aid testing.  Additionally the

"conflictResolver" has been "moved" to the new "config" prop.  The old parameter pass through method

still works but can be considered deprecated.

perf(optimisations): ComponentQueries has been optimised to behave li…

…ke a "pure" component.

BREAKING CHANGE: This is a *partially* breaking change that I don't expect will affect most users. I have extended the HOC so that it acts like a pure component.  In doing so it checks to see if either the result of the queries are new or new _additional_ props have been passed into your wrapped component. The `render` then only fires if one of these conditions were met. You can override this behaviour by using the new complex configuration option:
`componentQueries({ queries: [...], config: { pure: false }})`
The new `config` prop includes the `pure` option as shown above as well as all the properties from the `sizeMeConfig` configuration prop (which is to be deprecated).

I've had to do a placeholder commit here as I previously got the semantic-release format for commit message wrong.