Over the past 2 months we’ve been taking feedback and working hard to make React even better. We fixed some bugs, made some under-the-hood improvements, and added several features that we think will improve the experience developing with React. Today we’re proud to announce the availability of React v0.4!
\nThis release could not have happened without the support of our growing community. Since launch day, the community has contributed blog posts, questions to the Google Group, and issues and pull requests on GitHub. We’ve had contributions ranging from documentation improvements to major changes to React’s rendering. We’ve seen people integrate React into the tools they’re using and the products they’re building, and we’re all very excited to see what our budding community builds next!
\nReact v0.4 has some big changes. We’ve also restructured the documentation to better communicate how to use React. We’ve summarized the changes below and linked to documentation where we think it will be especially useful.
\nWhen you’re ready, go download it!
\nid attribute to data-reactid to track DOM nodes. This allows you to integrate with other JS and CSS libraries more easily.<canvas>)React.renderComponentToString(<component>, callback) allows you to use React on the server and generate markup which can be sent down to the browser.prop improvements: validation and default values. Read our blog post for details…key prop, which allows for finer control over reconciliation. Read the docs for details…React.autoBind. Read our blog post for details…<input>, <textarea>, <option>, and <select> in order to standardize many inconsistencies in browser implementations. This includes support for defaultValue, and improved implementation of the onChange event, and circuit completion. Read the docs for details…this.setState now takes an optional callback as its second parameter. If you were using onClick={this.setState.bind(this, state)} previously, you’ll want to make sure you add a third parameter so that the event is not treated as the callback.<div>{/* this is a comment and won't be rendered */}</div><div><Component1/><Component2/></div> is transformed into React.DOM.div(null, Component1(null), Component2(null)).\nPreviously this would be transformed into React.DOM.div(null, [Component1(null), Component2(null)]).\nIf you were using React without JSX previously, your code should still work.require()s to be relative unless specified