Recommend Node v0.10.0 due to https://github.com/isaacs/npm/issues/2907
Merge pull request #132 from petehunt/engines

Recommend Node v0.10.0 due to https://github.com/isaacs/npm/issues/2907
Community Roundup #3
Merge pull request #126 from vjeux/community_3

Community Roundup #3
Add @jsx common parser issues in the docs

Update getting-started.md
Bump version to 0.4.0a

This should have happened a while ago, but better late than never.
Fix `findComponentRoot` w/ Unidentified Nodes

The current `ReactInstanceHandles` has a bug where `findComponentRoot` barfs if it comes across a node that was not identified by React (via `ReactID`). This fixes that.

This was always a bug, but it became more apparent once we switched to `data-reactid` because arbitrary `document.createElement`'d nodes are much more likely to have an `id` than they are to have a `data-reactid`.
Merge pull request #123 from vjeux/patch-2

Add @jsx common parser issues in the docs
Add link roundup
Merge pull request #135 from vjeux/bugbuster

Add link roundup
Add support for empty XJS expressions
Fix Composition Level of Components w/o Owners

This fixes a bug with components constructed with no owners, for example:

  // Both the <div> and <span> have no owners.
  React.renderComponent(<div><span /></div>, node);

They should have a composition level of 1 and their keys should be prefixed with 0 to indicate they were created without owners. However, they currently incorrectly get a composition level of 0 (which means that //their// children will have keys prefixed with 0, which is wrong).
Throw on Missing Elements

This changes React to throw when `ReactID.getNode()` fails to find a node. This method is used by two call sites:

 - Implements `ReactComponent#getDOMNode`. This method already throws if a component is not mounted, and //all mounted components should be able to find their rendered root nodes//.
 - Used by `ReactDOMIDOperations`. These call sites aleady assume that `getNode` returns a non-null. Currently, if the node is not found, this is the site that fatals (and the stack trace is much harder to debug).

The error message should make it //a lot// easier to debug unexpected DOM trees. In particular, this will help track down all the places where the browser inserts `<tbody>` unexpectedly.
.reactRoot[base10] -> .r[base36]

Just a bit of byte savings for server rendering. Props to @benjamn for the base36 idea (and for making this diff easy).

With a little work we could probably get rid of the .r as well.
Merge pull request #136 from jeffmo/empty_expressions

Add support for empty XJS expressions
Merge branch 'textarea-update-value' of git://github.com/spicyj/react

Conflicts:
	src/core/ReactDefaultInjection.js
Delete files that accidentally got merged in

ಠ_ಠ
Clean up unused variables for lint
Improve `findComponentRoot` Error Message

Instead of simply logging the React ID of the `ancestorNode` when `findComponentRoot` fails, use a `try ... finally` to `console.error` the `ancestorNode`. This allows modern web inspectors to actually log a reference to the node (which may not have a React ID).

This means when people run into the problem, they will not have to execute:

  require('ReactID').getNode(<copy+paste>);

NOTE: Admittedly, this will not log anything in IE8. That's fine, since IE8 has shitty console logging anyway.
Implement `ReactDOMTextarea`

This changes `ReactDOMTextarea` to accept `defaultValue` and `value`. It will warn people about using children (but allow it and treat it as `defaultValue`, which is the current behavior).