Use grunt.util.spawn for jsx:* tasks instead of exec.

This should prevent "Warning: stdout maxBuffer exceeded" errors.

Also piping child process stdout and stderr to the parent process, so
you can see more of what's happening during the build process.
Merge pull request #102 from zpao/fix-transformer

Improve JSXTransformer
Merge pull request #103 from benjamn/fix-maxBuffer-exceeded

Use grunt.util.spawn for jsx:* tasks instead of exec
Use Node Cache in ReactComponent

There are currently two places where we lookup and cache nodes: `ReactDOMNodeCache` and `ReactComponent`. Instead, we should just consolidate caches and make `ReactComponent` use `ReactDOMNodeCache`.
Remove trailing whitespace
React onlyChild utility.

Small utility that extracts and validates that there is only a single
child passed to a React composite component. The benefit here is that we
abstract away *how* the children are actually stored while we iterate on
different approaches. This way we won't break callsites as we try different
ideas. When we settle on a final approach, all of these callsites will still
work.
Fix `EventPluginRegistry` Unit Tests in GitHub

Dumping the mock cache isn't dirying the modules in the open source version, so we have to unit test a different way. If we can fix the unit test framework, we should revert this.

Also, I added strict mode to `EventPluginRegistry.js`.

See: https://github.com/facebook/react/pull/91
Use Synthetic Events

Swaps out usage of `AbstractEvent` with `SyntheticEvent` (and subclasses).
Add Back `DOMCharacterDataModified`

Accidentally lost `DOMCharacterDataModified`.
Add missing license header.
Fixing known keying problems

This fixes the last known parts of the flattening experiment. This has grown to
be somewhat complex and potentially fragile because of it. We may end up
reverting flattening in the future or address it slightly differently.

The purpose of this diff is to test if we've finally understood the real world
edge cases that flattening can lead to and how we have to key components to
cover those cases.

With this commit we never rekey the internal _key property. The semantics is
that once a component passes through a composite component, it's identity is
frozen.

props.key should accept numeric values and booleans which includes 0 and false.
This fixes the truthiness check.

We should never warn about missing key properties if a component is passed as a
static child. The _key acts as a flag to determine whether this component
was checked already.
Add missing license header
Upgrade Recast to 0.4.8 to fix options.writeback bug.

Bug introduced by: https://github.com/benjamn/recast/commit/e913b22f8f
Bug fixed by: https://github.com/benjamn/recast/commit/170e18091e
Merge pull request #105 from benjamn/fix-options.writeback-bug

Upgrade Recast to 0.4.8 to fix options.writeback bug
Cleanup lint warnings

Mostly trivial things that should have been caught upstream.