2.1.2

<a name"2.1.2">

2.1.2 (2016-07-25)

Bug Fixes

• Removes relative styling on temporary div instance. (3ad5a57b, closes #20)

2.1.1

<a name"2.1.1">

2.1.1 (2016-06-23)

Bug Fixes

• SizeMe: Updated the dependencies and exposed WrappedComponent as a static prop on SizeMe (244bc9a4)

2.1.0

<a name"2.1.0">

2.1.0 (2016-05-23)

Features

• server: Added semi-support for Server Side Rendering (8aab588c)

2.0.3

<a name"2.0.3">

2.0.3 (2016-05-21)

Bug Fixes

• browser: Resize Detector is now lazily used in order to prevent #6. Thanks @tonyxiao! (32b64bab)

2.0.2

<a name"2.0.2">

2.0.2 (2016-05-19)

Patches

• dependencies: Updated dependencies and introduced webpack-lodash-plugin. (e5be0d19)

2.0.1

<a name"2.0.1">

2.0.1 (2016-05-16)

Bug Fixes

• core: Fixed issue with possible element checking after component has been unmounted. (9032ea3c)

2.0.0

<a name"2.0.0">

2.0.0 (2016-04-19)

Breaking Changes

Okay, sorry about this, but I have decided to release a breaking change. That being said I think it's unlikely to affect many people.

I've realised that I may be causing some confusion by always providing width/height values even if you aren't monitoring one of the dimensions. If you mistakenly rely on a dimension that isn't being monitored this may lead to gremlins in your code. Therefore I have decided to provide null values for any dimension that is not being monitored.

By default we only monitor width, therefore if you would like to get values for height change the configuration for your SizeMe HOC to:
SizeMe({ monitorHeight: true })(YourComponent);

(24b49cdf)

v1.0.6

<a name"1.0.6">

1.0.6 (2016-04-18)

Bug Fixes

• Behaviour: Size changes are now throttled with head and tail execution. (726259c3, closes #4)

v1.0.5

<a name"1.0.5">

1.0.5 (2016-04-15)

Bug Fixes

• dependencies: Fixed dependencies in package.json (de5f796b)

v1.0.4

<a name"1.0.4">

1.0.4 (2016-04-15)

Bug Fixes

• bug: Invalid propType validation within internals. (24672e17)