Allow to execute JSXTransformer outside of browser environment
upgrade example to 0.4

manually tested
Merge pull request #218 from chenglou/patch-2

upgrade example to 0.4
Add comment explaining internalGetID
Remove unused dependency on ReactMount

We don't really use these, and this will make our lives easier.
Don't set DOM attributes to `"undefined"` on update

We already skip `null` and `undefined` when building up the stringified html on first render, but if you update a component to the *exact same* conditions, React will leave the DOM in a different state. We shouldn't do that.
Push builds from travis to remote host
Run `grunt build` with `npm test` so that we can upload all files
Fix TypeError in SyntheticEvent

I suspect that plugins are modifying `Object.prototype` which is causing TypeErrors in `SyntheticEvent`. Let's fix it.
Fix Clicks in Mobile Safari

This works around a bug with listening to clicks using event delegation on Mobile Safari using an event plugin.

NOTE: We don't enable touch events by default, so I don't know if would want to inject this plugin by default. In fact, I'm not sure what our strategy is at all for when to invoke `React.useTouchEvents(true)`.
Call callbacks from setState in component context

This is way more useful than the alternative.
Community Round-up #5

http://fooo.fr:4000/react/blog/2013/07/20/community-roundup-5.html
Use the right home page for react-source gem
fix jquery-bootstrap example bugs

Old one had some bugs:
- 'x' on modal wasn't showing.
- trying to close modal in unmount, but modal had a closing animation.
Merge remote branch 'upstream/master' into non-browser-env
Do not export load in JSXTransformer unless in a browser environment
Merge pull request #217 from jakubmal/non-browser-env

Allow to execute JSXTransformer outside of browser environment
Fix "Suppport" type in docs
Fix OrderedMap.

Tim caught a bug. Squashing it so he can rebase on top of it.
Warn when server-rendered markup is not what we expect on the client

As @leebyron and balpert pointed out, if the markup on the server is differnet than what the client expects undefined behavior and chaos may ensue. A good fallback
is for us to just inject the client-side markup (as it is the source of truth) and warn the user in __DEV__ that something is wrong. In order to do a fast
browser-independent check of the DOM I use an adler32 checksum of the generated markup. I believe this is better than a simple innerHTML compare because different
browsers massage innerHTML differently.