Error when unmountComponentAtNode receives non-node
ballmer-peak: use composition instead of mutable state
fix: var name
Inject the runtime to a global instead of exposing internals

See https://github.com/facebook/react-devtools/commit/673de20a4a0654ab849575307b9cf87fde53439e
Merge pull request #2337 from sebmarkbage/devtoolshook

Inject the runtime to a global instead of exposing internals
Update @emails in react-displayName-test
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)