jsx whitespace codemod utility
Add warning about object property order.

It's easy to misuse the properties-as-keys feature and end up with children rendered out of order. Add a note and example of how to avoid this.
Refactor ReactMultiChild to not throw errors too

Missed these when I fixed up Transaction; with the exception of ReactErrorUtils, this should be everything.
Add seamless and sandbox properties for iframe

Fixes #1057.
Assert that event listeners are real functions

Fixes #1028.
Measure root component render in ReactDefaultPerf

Fixes #1074.
Don't warn about onChange for button inputs
Remove old whitespace doc warning

This was fixed by #480.
Add onError to ReactDOMImg to complement onLoad
Merge pull request #1076 from spicyj/button-warn

Don't warn about onChange for button inputs
Merge pull request #1069 from spicyj/gh-1028

Assert that event listeners are real functions
Merge pull request #1067 from spicyj/sandbox-seamless

Add seamless and sandbox properties for iframe
Merge pull request #855 from syranide/onerror

Add onError to ReactDOMImg to complement onLoad
Merge pull request #1075 from spicyj/defperf

Measure root component render in ReactDefaultPerf
Merge pull request #979 from jeffmo/jsx_whitespace_codemod_tool

jsx whitespace codemod utility
Move jsx_whitespace_transform

Also add readme and more details to package.json so it can be published.
Remove aural CSS numerial styles from CSSProperties

Those styles are not implemented in known browsers.
Updates to perf

ReactDefaultPerf:

* Show times as float instead of string. This means they're sortable.
* Add count columns to all types and average to exclusive time.
* Include mountComponent where updateComponent time is measured.
* Increment count on _renderValidatedComponent instead of update.

ReactDefaultPerfAnalysis:

* Return counts with all summaries.
un-revert textContent, support multi-line strings in modern browsers

reverts 23ab30ff873fba816129cafa0c40112dd2ee990d because the issue it fixed doesn't seem to be a problem
anymore. textContent should be better for more things anyway, as the
original 309a88bcf62c1c64a2b91c0eb753c19209a425b2 indicates. It should be faster because innerText
requires layout.

This also allows us to use strings with newlines in our rendered output
and have confidence that they will render the same on subsequent
re-renders. This is especially useful for es6-style backtick multi-line
strings. This will be more consistent as textContent is supported almost
everwhere so we won't have differing behavior between webkit and
firefox.

see https://github.com/facebook/react/issues/1080
Tweak whitespace README to show other change