1.0.3

CHANGELOG.md

@@ -1,5 +1,9 @@
 ## Changelog
 
+### 1.0.3
+
+* In addition to hotifying `module.exports` by default, also hotify all its own properties
+
 ### 1.0.2
 
 * Don't try to hot-replace `module.export`ed `ReactElement`s

docs/README.md

@@ -19,9 +19,9 @@ React Hot Loader has reached 1.0, and it's a breaking change. When React Hot Loa
 
 Here's how we're solving these problems in 1.0:
 
-#### Only `module.exports` is hot by default
+#### Only `module.exports` and its own properties are hot by default
 
-With 1.0, we no longer parse your sources. Instead, we only now make `module.exports` hot by default, and only if it has a prototype declaring `render` method. **If you've been splitting each component in a separate file, that means no change for you here!** This allows us to support exotic wrappers and ES6 classes when they come out.
+With 1.0, we no longer parse your sources. Instead, we only now make `module.exports` and its [own properties](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Object/hasOwnProperty) hot by default, and only if their prototype declares `render` method. **If you've been splitting each component in a separate file, that means no change for you here!** This allows us to support exotic wrappers and ES6 classes when they come out.
 
 #### You can make hot anything else via opt-in `module.makeHot` API
 

package.json

@@ -1,6 +1,6 @@
 {
   "name": "react-hot-loader",
-  "version": "1.0.2",
+  "version": "1.0.3",
   "description": "Live edit React components without unmounting or losing their state (a Webpack loader)",
   "main": "index.js",
   "dependencies": {