Error when unmountComponentAtNode receives non-node
ballmer-peak: use composition instead of mutable state
fix: var name
Ship merge to npm

People may have a bad time if they're depending on these but we can
delay that a little bit. Unless they're using directly and not
polyfilling Object.assign.
Use react.createElement in example in basic/
Merge pull request #2317 from zpao/npm-ship-merge

Ship merge, mergeInto, copyProperties to npm
React Elements blog post
Update dependencies, removed unused ones

Also picked up a bit of JSON reformatting, presumably from npm >= 2

Test plan: build, run tests
Update PropTypes for ReactElement & ReactNode
browserify update
Merge pull request #2349 from zpao/update-deps

Update npm dependencies, fix browserify task
Merge pull request #2343 from zpao/proptypes-deprecation

Update PropTypes for ReactElement & ReactNode
Merge pull request #2330 from alexeyraspopov/patch-1

use function composition instead of mutable state
#2315 : Use of React.createFactory in example basic/
Fix typo in blog post
Merge pull request #2344 from ThomasCrvsr/master

Use React.createFactory in examples/basic/
0.11.2 release materials

TODO: starter kit for cherry-pick to master
(cherry picked from commit 732ffad3137773e72ca587decd20d2aff85200a2)
[docs] Move React Elements post to right place, fix typo

The URL already made its way around so we can't just break it. We might
want to just live with it instead of even doing this redirect.

https://github.com/plaxdan/react/commit/2b225446c03192b58e176f8885e60055cf5ea436#commitcomment-8176218
Merge pull request #2359 from zpao/fix-blog-post

[docs] Move React Elements post to right place, fix typo
minor change to post

Hello,

I was just reading through your post and noticed a minor change. The sentence originally read, "It's scaled very well for us...". I thought it was a little unclear since it's can mean "it has" or "it is", which can make this sentence take on a whole different meaning.