Created
September 10, 2015 00:32
-
-
Save zpao/a11adf27d2432f473847 to your computer and use it in GitHub Desktop.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| --- _site/feed_old.xml 2015-09-09 17:31:09.000000000 -0700 | |
| +++ _site/feed.xml 2015-09-09 17:31:04.000000000 -0700 | |
| @@ -1,19 +1,24 @@ | |
| -<?xml version="1.0" encoding="UTF-8"?> | |
| -<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> | |
| - <channel> | |
| - <title>React</title> | |
| - <description>A JavaScript library for building user interfaces</description> | |
| - <link>https://facebook.github.io/react</link> | |
| - <atom:link href="https://facebook.github.io/react/feed.xml" rel="self" type="application/rss+xml" /> | |
| - | |
| - <item> | |
| - <title>New React Developer Tools</title> | |
| - <description><p>A month ago, we <a href="/react/blog/2015/08/03/new-react-devtools-beta.html">posted a beta</a> of the new React developer tools. Today, we&#39;re releasing the first stable version of the new devtools. We&#39;re calling it version 0.14, but it&#39;s a full rewrite so we think of it more like a 2.0 release.</p> | |
| +<?xml version="1.0" encoding="utf-8"?> | |
| +<feed xmlns="http://www.w3.org/2005/Atom"> | |
| +<generator uri="http://jekyllrb.com" version="2.2.0">Jekyll</generator> | |
| +<link href="https://facebook.github.io/react/feed.xml" rel="self" type="application/atom+xml" /> | |
| +<link href="https://facebook.github.io/react/" rel="alternate" type="text/html" /> | |
| +<updated>2015-09-09T17:31:03-07:00</updated> | |
| +<id>https://facebook.github.io/react/</id> | |
| +<title>React</title> | |
| +<subtitle>A JavaScript library for building user interfaces</subtitle> | |
| +<entry> | |
| +<title>New React Developer Tools</title> | |
| +<link href="https://facebook.github.io/react/blog/2015/09/02/new-react-developer-tools.html" rel="alternate" type="text/html" title="New React Developer Tools" /> | |
| +<published>2015-09-02T00:00:00-07:00</published> | |
| +<updated>2015-09-02T00:00:00-07:00</updated> | |
| +<id>https://facebook.github.io/react/blog/2015/09/02/new-react-developer-tools</id> | |
| +<content type="html" xml:base="https://facebook.github.io/react/blog/2015/09/02/new-react-developer-tools.html"><p>A month ago, we <a href="/react/blog/2015/08/03/new-react-devtools-beta.html">posted a beta</a> of the new React developer tools. Today, we&#39;re releasing the first stable version of the new devtools. We&#39;re calling it version 0.14, but it&#39;s a full rewrite so we think of it more like a 2.0 release.</p> | |
| <p><img src="/react/img/blog/devtools-full.gif" alt="Video/screenshot of new devtools"></p> | |
| <p>It contains a handful of new features, including:</p> | |
| <ul> | |
| <li>Built entirely with React, making it easier to develop and extend</li> | |
| <li>Firefox support</li> | |
| @@ -24,25 +29,30 @@ | |
| <li>Full React Native support</li> | |
| </ul> | |
| <h2><a class="anchor" name="installation"></a>Installation <a class="hash-link" href="#installation">#</a></h2> | |
| <p>Download the new devtools from the <a href="https://chrome.google.com/webstore/detail/react-developer-tools/fmkadmapgofadopljbjfkapdkoienihi">Chrome Web Store</a> and on <a href="https://addons.mozilla.org/en-US/firefox/addon/react-devtools/">Mozilla Add-ons</a> for Firefox. If you&#39;re developing using React, we highly recommend installing these devtools.</p> | |
| <p>If you already have the Chrome extension installed, it should autoupdate within the next week. You can also head to <code>chrome://extensions</code> and click &quot;Update extensions now&quot; if you&#39;d like to get the new version today. If you installed the devtools beta, please remove it and switch back to the version from the store to make sure you always get the latest updates and bug fixes.</p> | |
| <p>If you run into any issues, please post them on our <a href="https://github.com/facebook/react-devtools">react-devtools GitHub repo</a>.</p> | |
| -</description> | |
| - <pubDate>2015-09-02T00:00:00-07:00</pubDate> | |
| - <link>https://facebook.github.io/react/blog/2015/09/02/new-react-developer-tools.html</link> | |
| - <guid isPermaLink="true">https://facebook.github.io/react/blog/2015/09/02/new-react-developer-tools.html</guid> | |
| - </item> | |
| - | |
| - <item> | |
| - <title>ReactEurope Round-up</title> | |
| - <description><p>Last month, the first React.js European conference took place in the city of Paris, at ReactEurope. Attendees were treated to a range of talks covering React, React Native, Flux, Relay, and GraphQL. Big thanks to everyone involved with organizing the conference, to all the attendees, and everyone who gave their time to speak - it wouldn&#39;t have been possible without the help and support of the React community.</p> | |
| +</content> | |
| +<author> | |
| +<name>Ben Alpert</name> | |
| +<uri>http://benalpert.com</uri> | |
| +</author> | |
| +<summary>A month ago, we posted a beta of the new React developer tools. Today, we&#39;re releasing the first stable version of the new devtools. We&#39;re calling it version 0.14, but it&#39;s a full rewrite so we think of it more like a 2.0 release.It contains a handful of new features, including:Built entirely with React, making it easier to develop and extendFirefox supportSelected component instance is available as $r from the consoleMore detail is shown in props in the component treeRight-click any node and choose &quot;Show Source&quot; to jump to the render method in the Sources panelRight-click any props or state value to make it available as $tmp from the consoleFull React Native supportInstallation #Download the new devtools from the Chrome Web Store and on Mozilla Add-ons for Firefox. If you&#39;re developing using React, we highly recommend installing these devtools.If you already have the Chrome extension installed, it should autoupdate within the next week. You can also head to chrome://extensions and click &quot;Update extensions now&quot; if you&#39;d like to get the new version today. If you installed the devtools beta, please remove it and switch back to the version from the store to make sure you always get the latest updates and bug fixes.If you run into any issues, please post them on our react-devtools GitHub repo.</summary> | |
| +</entry> | |
| +<entry> | |
| +<title>ReactEurope Round-up</title> | |
| +<link href="https://facebook.github.io/react/blog/2015/08/13/reacteurope-roundup.html" rel="alternate" type="text/html" title="ReactEurope Round-up" /> | |
| +<published>2015-08-13T00:00:00-07:00</published> | |
| +<updated>2015-08-13T00:00:00-07:00</updated> | |
| +<id>https://facebook.github.io/react/blog/2015/08/13/reacteurope-roundup</id> | |
| +<content type="html" xml:base="https://facebook.github.io/react/blog/2015/08/13/reacteurope-roundup.html"><p>Last month, the first React.js European conference took place in the city of Paris, at ReactEurope. Attendees were treated to a range of talks covering React, React Native, Flux, Relay, and GraphQL. Big thanks to everyone involved with organizing the conference, to all the attendees, and everyone who gave their time to speak - it wouldn&#39;t have been possible without the help and support of the React community.</p> | |
| <p><a href="https://github.com/vjeux">Christopher Chedeau</a> gave the opening keynote to the conference:</p> | |
| <iframe width="650" height="366" src="//www.youtube.com/embed/PAA9O4E1IM4" frameborder="0" allowfullscreen></iframe> | |
| <p><a href="https://github.com/sahrens">Spencer Ahrens</a> walks through building an advanced gestural UI leveraging the unique power of the React Native layout and animation systems to build a complex and fluid experience:</p> | |
| <iframe width="650" height="366" src="//www.youtube.com/embed/xDlfrcM6YBk" frameborder="0" allowfullscreen></iframe> | |
| @@ -90,25 +100,30 @@ | |
| <li><a href="https://www.youtube.com/watch?v=2Qu-Ulrsfl8&amp;index=8&amp;list=PLCC436JpVnK3HvUSAHpt-LRJkIK8pQG6R">Aria Buckles</a> covers Khan Academy&#39;s techniques and patterns to make dealing with large pure components simpler, as well as current open questions.</li> | |
| <li><a href="https://www.youtube.com/watch?v=Uu4Yz2HmCgE&amp;index=9&amp;list=PLCC436JpVnK3HvUSAHpt-LRJkIK8pQG6R">Evan Morikawa and Ben Gotow</a> talk about specific features of React &amp; Flux, React CSS, programming design patterns, and custom libraries, which can turn a static application into a dynamic platform that an ecosystem of developers can build on top of.</li> | |
| <li><a href="https://www.youtube.com/watch?v=3EQhkquvVmY&amp;list=PLCC436JpVnK0Phxld2dD4tM4xPMxJCiRD&amp;index=9">Zalando</a>, <a href="https://www.youtube.com/watch?v=nAWKR1bBDsU&amp;index=12&amp;list=PLCC436JpVnK0Phxld2dD4tM4xPMxJCiRD">Rangle.io</a>, <a href="https://www.youtube.com/watch?v=hjhyrBbDp6U&amp;index=13&amp;list=PLCC436JpVnK0Phxld2dD4tM4xPMxJCiRD">Automattic</a>, <a href="https://www.youtube.com/watch?v=ApoCktYaRxk&amp;list=PLCC436JpVnK0Phxld2dD4tM4xPMxJCiRD&amp;index=14">Thinkmill</a>, and <a href="https://www.youtube.com/watch?v=hdKidiwR8DM&amp;list=PLCC436JpVnK0Phxld2dD4tM4xPMxJCiRD&amp;index=15">Red Badger</a> provided lots of insight into how larger companies are using React.</li> | |
| </ul> | |
| <p>There was also a <a href="https://www.youtube.com/playlist?list=PLCC436JpVnK3xnOZ727t0vd3nbb5ZqCyo">great series of Lightning talks</a> from <a href="https://github.com/jsierles">Joshua Sierles</a>, <a href="https://github.com/skidding">Ovidiu Cherecheș</a>, <a href="https://github.com/grabbou">Mike Grabowski</a>, <a href="https://github.com/bruderstein">Dave Brotherstone</a>, <a href="https://github.com/threepointone">Sunil Pai</a>, <a href="https://github.com/AnSavvides">Andreas Savvides</a>, and <a href="https://github.com/petrbela">Petr Bela</a>.</p> | |
| <p>You can view the full list of talks on <a href="https://www.youtube.com/channel/UCorlLn2oZfgOJ-FUcF2eZ1A">the ReactEurope YouTube channel</a>.</p> | |
| -</description> | |
| - <pubDate>2015-08-13T00:00:00-07:00</pubDate> | |
| - <link>https://facebook.github.io/react/blog/2015/08/13/reacteurope-roundup.html</link> | |
| - <guid isPermaLink="true">https://facebook.github.io/react/blog/2015/08/13/reacteurope-roundup.html</guid> | |
| - </item> | |
| - | |
| - <item> | |
| - <title>Relay Technical Preview</title> | |
| - <description><h1><a class="anchor" name="relay"></a>Relay <a class="hash-link" href="#relay">#</a></h1> | |
| +</content> | |
| +<author> | |
| +<name>Matthew Johnston</name> | |
| +<uri>https://github.com/matthewathome</uri> | |
| +</author> | |
| +<summary>Last month, the first React.js European conference took place in the city of Paris, at ReactEurope. Attendees were treated to a range of talks covering React, React Native, Flux, Relay, and GraphQL. Big thanks to everyone involved with organizing the conference, to all the attendees, and everyone who gave their time to speak - it wouldn&#39;t have been possible without the help and support of the React community.Christopher Chedeau gave the opening keynote to the conference:Spencer Ahrens walks through building an advanced gestural UI leveraging the unique power of the React Native layout and animation systems to build a complex and fluid experience:Lee Byron explores GraphQL, its core principles, how it works, and what makes it a powerful tool:Joseph Savona explores the problems Relay solves, its architecture and the query lifecycle, and how can you use Relay to build more scalable apps. There are examples of how Relay powers applications as complex as the Facebook News Feed:Nick Schrock and Dan Schafer take a deeper dive into putting GraphQL to work. How can we build a GraphQL API to work with an existing REST API or server-side data model? What are best practices when building a GraphQL API, and how do they differ from traditional REST best practices? How does Facebook use GraphQL? Most importantly, what does a complete and coherent GraphQL API looks like, and how can we get started building one?Sebastian Markbåge talks about why the DOM is flawed and how it is becoming a second-class citizen in the land of React apps:Sebastian McKenzie goes over how existing JSX build pipeline infrastructure can be further utilised to perform even more significant code transformations such as transpilation, optimisation, profiling and more, reducing bugs, making your code faster and you as a developer more productive and happy:Cheng Lou gives a talk on the past, the present and the future of animation, and the place React can potentially take in this:And there was a Q&amp;A session with the whole team covering a range of React topics:And there were lots of great talks from the React community:Michael Chan looks at how to solve problems like CSS theming and media queries with contexts and plain old JavaScript. He also looks at the role of container-components and when it&#39;s better to &quot;just use CSS.&quot;.Elie Rotenberg talks about Flux over the Wire, building isomorphic, real-time React apps using a novel interpretation of Flux.Ryan Florence says “Your front and back ends are already successfully in production but you don&#39;t have to miss out on the productivity that React brings. Forget the rewrites, this is brownfield!”.Dan Abramov demonstrates how React can be used together with Webpack Hot Module Replacement to create a live editing environment with time travel that supercharges your debugging experience and transforms the way you work on real apps every day.Mikhail Davydov shows you how to ask the browser layout engine for help, how to avoid slavery of DSL, and build declarative Text UI using only web-technologies like HTML, JS, CSS and React.Kevin Robinson shares how user experience choices are a primary influence on how Twitter design the data layer, especially for teams developing new products with full-stack capabilities.Jed Watson shares what Thinkmill have learned about React and mobile app development, and how they&#39;ve approached the unique challenges of mobile web apps - with tools that are useful to all developers building touch interfaces with React, as well as a walkthrough of their development process and framework.Michael Jackson discusses how your users can benefit from the many tools that React Router provides including server-side rendering, real URLs on native devices, and much, much more.Michael Ridgway walks you through an isomorphic Flux architecture to give you the holy grail of frontend development.Aria Buckles covers Khan Academy&#39;s techniques and patterns to make dealing with large pure components simpler, as well as current open questions.Evan Morikawa and Ben Gotow talk about specific features of React &amp; Flux, React CSS, programming design patterns, and custom libraries, which can turn a static application into a dynamic platform that an ecosystem of developers can build on top of.Zalando, Rangle.io, Automattic, Thinkmill, and Red Badger provided lots of insight into how larger companies are using React.There was also a great series of Lightning talks from Joshua Sierles, Ovidiu Cherecheș, Mike Grabowski, Dave Brotherstone, Sunil Pai, Andreas Savvides, and Petr Bela.You can view the full list of talks on the ReactEurope YouTube channel.</summary> | |
| +</entry> | |
| +<entry> | |
| +<title>Relay Technical Preview</title> | |
| +<link href="https://facebook.github.io/react/blog/2015/08/11/relay-technical-preview.html" rel="alternate" type="text/html" title="Relay Technical Preview" /> | |
| +<published>2015-08-11T00:00:00-07:00</published> | |
| +<updated>2015-08-11T00:00:00-07:00</updated> | |
| +<id>https://facebook.github.io/react/blog/2015/08/11/relay-technical-preview</id> | |
| +<content type="html" xml:base="https://facebook.github.io/react/blog/2015/08/11/relay-technical-preview.html"><h1><a class="anchor" name="relay"></a>Relay <a class="hash-link" href="#relay">#</a></h1> | |
| <p>Today we&#39;re excited to share an update on Relay - the technical preview is now open-source and <a href="http://github.com/facebook/relay">available on GitHub</a>.</p> | |
| <h2><a class="anchor" name="why-relay"></a>Why Relay <a class="hash-link" href="#why-relay">#</a></h2> | |
| <p>While React simplified the process of developing complex user-interfaces, it left open the question of how to interact with data on the server. It turns out that this was a significant source of friction for our developers; fragile coupling between client and server caused data-related bugs and made iteration harder. Furthermore, developers were forced to constantly re-implement complex async logic instead of focusing on their apps. Relay addresses these concerns by borrowing important lessons from React: it provides <em>declarative, component-oriented data fetching for React applications</em>.</p> | |
| <p>Declarative data-fetching means that Relay applications specify <em>what</em> data they need, not <em>how</em> to fetch that data. Just as React uses a description of the desired UI to manage view updates, Relay uses a data description in the form of GraphQL queries. Given these descriptions, Relay coalesces queries into batches for efficiency, manages error-prone asynchronous logic, caches data for performance, and automatically updates views as data changes.</p> | |
| <p>Relay is also component-oriented, extending the notion of a React component to include a description of what data is necessary to render it. This colocation allows developers to reason locally about their application and eliminates bugs such as under- or over-fetching data.</p> | |
| @@ -123,25 +138,30 @@ | |
| <ul> | |
| <li>Offline support. This will allow applications to fulfill queries and enqueue updates without connectivity.</li> | |
| <li>Real-time updates. In collaboration with the GraphQL community, we&#39;re working to define a specification for subscriptions and provide support for them in Relay.</li> | |
| <li>A generic Relay. Just as the power of React was never about the virtual DOM, Relay is much more than a GraphQL client. We&#39;re working to extend Relay to provide a unified interface for interacting not only with server data, but also in-memory and native device data (and, even better, a mix of all three).</li> | |
| <li>Finally, it&#39;s all too easy as developers to focus on those people with the newest devices and fastest internet connections. We&#39;re working to make it easier to build applications that are robust in the face of slow or intermittent connectivity.</li> | |
| </ul> | |
| <p>Thanks!</p> | |
| -</description> | |
| - <pubDate>2015-08-11T00:00:00-07:00</pubDate> | |
| - <link>https://facebook.github.io/react/blog/2015/08/11/relay-technical-preview.html</link> | |
| - <guid isPermaLink="true">https://facebook.github.io/react/blog/2015/08/11/relay-technical-preview.html</guid> | |
| - </item> | |
| - | |
| - <item> | |
| - <title>New React Devtools Beta</title> | |
| - <description><p>We&#39;ve made an entirely new version of the devtools, and we want you to try it | |
| +</content> | |
| +<author> | |
| +<name>Joseph Savona</name> | |
| +<uri>https://twitter.com/en_JS</uri> | |
| +</author> | |
| +<summary>Relay #Today we&#39;re excited to share an update on Relay - the technical preview is now open-source and available on GitHub.Why Relay #While React simplified the process of developing complex user-interfaces, it left open the question of how to interact with data on the server. It turns out that this was a significant source of friction for our developers; fragile coupling between client and server caused data-related bugs and made iteration harder. Furthermore, developers were forced to constantly re-implement complex async logic instead of focusing on their apps. Relay addresses these concerns by borrowing important lessons from React: it provides declarative, component-oriented data fetching for React applications.Declarative data-fetching means that Relay applications specify what data they need, not how to fetch that data. Just as React uses a description of the desired UI to manage view updates, Relay uses a data description in the form of GraphQL queries. Given these descriptions, Relay coalesces queries into batches for efficiency, manages error-prone asynchronous logic, caches data for performance, and automatically updates views as data changes.Relay is also component-oriented, extending the notion of a React component to include a description of what data is necessary to render it. This colocation allows developers to reason locally about their application and eliminates bugs such as under- or over-fetching data.Relay is in use at Facebook in production apps, and we&#39;re using it more and more because Relay lets developers focus on their products and move fast. It&#39;s working for us and we&#39;d like to share it with the community.What&#39;s Included #We&#39;re open-sourcing a technical preview of Relay - the core framework that we use internally, with some modifications for use outside Facebook. As this is the first release, it&#39;s good to keep in mind that there may be some incomplete or missing features. We&#39;ll continue to develop Relay and are working closely with the GraphQL community to ensure that Relay tracks updates during GraphQL&#39;s RFC period. But we couldn&#39;t wait any longer to get this in your hands, and we&#39;re looking forward to your feedback and contributions.Relay is available on GitHub and npm.What&#39;s Next #The team is super excited to be releasing Relay - and just as excited about what&#39;s next. Here are some of the things we&#39;ll be focusing on:Offline support. This will allow applications to fulfill queries and enqueue updates without connectivity.Real-time updates. In collaboration with the GraphQL community, we&#39;re working to define a specification for subscriptions and provide support for them in Relay.A generic Relay. Just as the power of React was never about the virtual DOM, Relay is much more than a GraphQL client. We&#39;re working to extend Relay to provide a unified interface for interacting not only with server data, but also in-memory and native device data (and, even better, a mix of all three).Finally, it&#39;s all too easy as developers to focus on those people with the newest devices and fastest internet connections. We&#39;re working to make it easier to build applications that are robust in the face of slow or intermittent connectivity.Thanks!</summary> | |
| +</entry> | |
| +<entry> | |
| +<title>New React Devtools Beta</title> | |
| +<link href="https://facebook.github.io/react/blog/2015/08/03/new-react-devtools-beta.html" rel="alternate" type="text/html" title="New React Devtools Beta" /> | |
| +<published>2015-08-03T00:00:00-07:00</published> | |
| +<updated>2015-08-03T00:00:00-07:00</updated> | |
| +<id>https://facebook.github.io/react/blog/2015/08/03/new-react-devtools-beta</id> | |
| +<content type="html" xml:base="https://facebook.github.io/react/blog/2015/08/03/new-react-devtools-beta.html"><p>We&#39;ve made an entirely new version of the devtools, and we want you to try it | |
| out!</p> | |
| <p><img src="/react/img/blog/devtools-full.gif" alt="The full devtools gif"></p> | |
| <h2><a class="anchor" name="why-entirely-new"></a>Why entirely new? <a class="hash-link" href="#why-entirely-new">#</a></h2> | |
| <p>Perhaps the biggest reason was to create a defined API for dealing with | |
| internals, so that other tools could benefit as well and not have to depend on | |
| implementation details. This gives us more freedom to refactor things | |
| internally without worrying about breaking tooling.</p> | |
| @@ -206,25 +226,30 @@ | |
| <a href="https://github.com/facebook/react-devtools/issues">on GitHub</a>, and check out | |
| <a href="https://github.com/facebook/react-devtools/tree/devtools-next">the README</a> | |
| for more info.</p> | |
| <h2><a class="anchor" name="update"></a>Update <a class="hash-link" href="#update">#</a></h2> | |
| <p><em>August 12, 2015</em></p> | |
| <p>A second beta is out, with a number of bugfixes. It is also listed on the | |
| <a href="https://github.com/facebook/react-devtools/releases">releases page</a>.</p> | |
| -</description> | |
| - <pubDate>2015-08-03T00:00:00-07:00</pubDate> | |
| - <link>https://facebook.github.io/react/blog/2015/08/03/new-react-devtools-beta.html</link> | |
| - <guid isPermaLink="true">https://facebook.github.io/react/blog/2015/08/03/new-react-devtools-beta.html</guid> | |
| - </item> | |
| - | |
| - <item> | |
| - <title>React v0.14 Beta 1</title> | |
| - <description><p>This week, many people in the React community are at <a href="https://www.react-europe.org/">ReactEurope</a> in the beautiful (and very warm) city of Paris, the second React conference that&#39;s been held to date. At our last conference, we released the first beta of React 0.13, and we figured we&#39;d do the same today with our first beta of React 0.14, giving you something to play with if you&#39;re not at the conference or you&#39;re looking for something to do on the way home.</p> | |
| +</content> | |
| +<author> | |
| +<name>Jared Forsyth</name> | |
| +<uri>https://twitter.com/jaredforsyth</uri> | |
| +</author> | |
| +<summary>We&#39;ve made an entirely new version of the devtools, and we want you to try itout!Why entirely new? #Perhaps the biggest reason was to create a defined API for dealing withinternals, so that other tools could benefit as well and not have to depend onimplementation details. This gives us more freedom to refactor thingsinternally without worrying about breaking tooling.The current version of the devtools is a fork of Blink&#39;s &quot;Elements&quot; pane, andis imperative, mutation-driven, and tightly integrated with Chrome-specificAPIs. The new devtools are much less coupled to Chrome, and easier to reasonabout thanks to React.What are the benefits? #100% ReactFirefox compatibleReact Native compatiblemore extensible &amp; hackableAre there any new features? #Yeah!The Tree View #Much richer view of your props, including the contents of objects and arraysCustom components are emphasized, native components are de-emphasizedStateful components have a red collapserImproved keyboard navigation (hjkl or arrow keys)Selected component is available in the console as $rProps that change highlight in greenRight-click menuScroll node into viewShow the source for a component in the &quot;Sources&quot; paneShow the element in the &quot;Elements&quot; paneSearching #Select the search bar (or press &quot;/&quot;), and start searching for a component byname.The Side Pane #Now shows the context for a componentRight-click to store a prop/state value as a global variableHow do I install it? #First, disable the Chrome web store version, or it will break things. Thendownload the .crx anddrag it into your chrome://extensions page. If it&#39;s not working to drag itfrom the downloads bar, try opening your downloads folder and drag it fromthere.Once we&#39;ve determined that there aren&#39;t any major regressions, we&#39;ll updatethe official web store version, and everyone will be automatically upgraded.Also Firefox! #We also have an initial version of the devtools for Firefox, which you candownload from the same release page.Feedback welcome #Let us know what issues you run intoon GitHub, and check outthe READMEfor more info.Update #August 12, 2015A second beta is out, with a number of bugfixes. It is also listed on thereleases page.</summary> | |
| +</entry> | |
| +<entry> | |
| +<title>React v0.14 Beta 1</title> | |
| +<link href="https://facebook.github.io/react/blog/2015/07/03/react-v0.14-beta-1.html" rel="alternate" type="text/html" title="React v0.14 Beta 1" /> | |
| +<published>2015-07-03T00:00:00-07:00</published> | |
| +<updated>2015-07-03T00:00:00-07:00</updated> | |
| +<id>https://facebook.github.io/react/blog/2015/07/03/react-v0.14-beta-1</id> | |
| +<content type="html" xml:base="https://facebook.github.io/react/blog/2015/07/03/react-v0.14-beta-1.html"><p>This week, many people in the React community are at <a href="https://www.react-europe.org/">ReactEurope</a> in the beautiful (and very warm) city of Paris, the second React conference that&#39;s been held to date. At our last conference, we released the first beta of React 0.13, and we figured we&#39;d do the same today with our first beta of React 0.14, giving you something to play with if you&#39;re not at the conference or you&#39;re looking for something to do on the way home.</p> | |
| <p>With React 0.14, we&#39;re continuing to let React mature and to make minor changes as the APIs continue to settle down. I&#39;ll talk only about the two largest changes in this blog post; when we publish the final release we&#39;ll be sure to update all of our documentation and include a full changelog.</p> | |
| <p>You can install the new beta with <code>npm install [email protected]</code> and <code>npm install [email protected]</code>. As mentioned in <a href="https://facebook.github.io/react/blog/2015/06/12/deprecating-jstransform-and-react-tools.html">Deprecating react-tools</a>, we&#39;re no longer updating the react-tools package so this release doesn&#39;t include a new version of it. Please try the new version out and let us know what you think, and please do file issues on our GitHub repo if you run into any problems.</p> | |
| <h2><a class="anchor" name="two-packages"></a>Two Packages <a class="hash-link" href="#two-packages">#</a></h2> | |
| <p>As we look at packages like <a href="https://github.com/facebook/react-native">react-native</a>, <a href="https://github.com/reactjs/react-art">react-art</a>, <a href="https://github.com/Flipboard/react-canvas">react-canvas</a>, and <a href="https://github.com/Izzimach/react-three">react-three</a>, it&#39;s become clear that the beauty and essence of React has nothing to do with browsers or the DOM.</p> | |
| <p>We think the true foundations of React are simply ideas of components and elements: being able to describe what you want to render in a declarative way. These are the pieces shared by all of these different packages. The parts of React specific to certain rendering targets aren&#39;t usually what we think of when we think of React. As one example, DOM diffing currently enables us to build React for the browser and make it fast enough to be useful, but if the DOM didn&#39;t have a stateful, imperative API, we might not need diffing at all.</p> | |
| @@ -274,50 +299,60 @@ | |
| <span class="p">}</span> | |
| <span class="p">});</span> | |
| </code></pre></div> | |
| <p>This change also applies to the return result of <code>ReactDOM.render</code> when passing a DOM node as the top component. As with refs, this change does not affect custom components (eg. <code>&lt;MyFancyMenu&gt;</code> or <code>&lt;MyContextProvider&gt;</code>), which remain unaffected by this change.</p> | |
| <p>Along with this change, we&#39;re also replacing <code>component.getDOMNode()</code> with <code>ReactDOM.findDOMNode(component)</code>. The <code>findDOMNode</code> method drills down to find which DOM node was rendered by a component, but it returns its argument when passed a DOM node so it&#39;s safe to call on a DOM component too. We introduced this function quietly in the last release, but now we&#39;re deprecating <code>.getDOMNode()</code> completely: it should be easy to change all existing calls in your code to be <code>ReactDOM.findDOMNode</code>. We also have an <a href="https://www.npmjs.com/package/react-codemod">automated codemod script</a> to help you with this transition. Note that the <code>findDOMNode</code> calls are unnecessary when you already have a DOM component ref (as in the example above), so you can (and should) skip them in most cases going forward.</p> | |
| <p>We hope you&#39;re as excited about this release as we are! Let us know what you think of it.</p> | |
| -</description> | |
| - <pubDate>2015-07-03T00:00:00-07:00</pubDate> | |
| - <link>https://facebook.github.io/react/blog/2015/07/03/react-v0.14-beta-1.html</link> | |
| - <guid isPermaLink="true">https://facebook.github.io/react/blog/2015/07/03/react-v0.14-beta-1.html</guid> | |
| - </item> | |
| - | |
| - <item> | |
| - <title>Deprecating JSTransform and react-tools</title> | |
| - <description><p>Today we&#39;re announcing the deprecation of react-tools and JSTransform.</p> | |
| +</content> | |
| +<author> | |
| +<name>Ben Alpert</name> | |
| +<uri>http://benalpert.com</uri> | |
| +</author> | |
| +<summary>This week, many people in the React community are at ReactEurope in the beautiful (and very warm) city of Paris, the second React conference that&#39;s been held to date. At our last conference, we released the first beta of React 0.13, and we figured we&#39;d do the same today with our first beta of React 0.14, giving you something to play with if you&#39;re not at the conference or you&#39;re looking for something to do on the way home.With React 0.14, we&#39;re continuing to let React mature and to make minor changes as the APIs continue to settle down. I&#39;ll talk only about the two largest changes in this blog post; when we publish the final release we&#39;ll be sure to update all of our documentation and include a full changelog.You can install the new beta with npm install [email protected] and npm install [email protected]. As mentioned in Deprecating react-tools, we&#39;re no longer updating the react-tools package so this release doesn&#39;t include a new version of it. Please try the new version out and let us know what you think, and please do file issues on our GitHub repo if you run into any problems.Two Packages #As we look at packages like react-native, react-art, react-canvas, and react-three, it&#39;s become clear that the beauty and essence of React has nothing to do with browsers or the DOM.We think the true foundations of React are simply ideas of components and elements: being able to describe what you want to render in a declarative way. These are the pieces shared by all of these different packages. The parts of React specific to certain rendering targets aren&#39;t usually what we think of when we think of React. As one example, DOM diffing currently enables us to build React for the browser and make it fast enough to be useful, but if the DOM didn&#39;t have a stateful, imperative API, we might not need diffing at all.To make this more clear and to make it easier to build more environments that React can render to, we&#39;re splitting the main react package into two: react and react-dom.The react package contains React.createElement, React.createClass and React.Component, React.PropTypes, React.Children, and the other helpers related to elements and component classes. We think of these as the isomorphic or universal helpers that you need to build components.The react-dom package contains ReactDOM.render, ReactDOM.unmountComponentAtNode, and ReactDOM.findDOMNode, and in react-dom/server we have server-side rendering support with ReactDOMServer.renderToString and ReactDOMServer.renderToStaticMarkup.var React = require(&#39;react&#39;);var ReactDOM = require(&#39;react-dom&#39;);var MyComponent = React.createClass({ render: function() { return &lt;div&gt;Hello World&lt;/div&gt;; }});ReactDOM.render(&lt;MyComponent /&gt;, node);We anticipate that most components will need to depend only on the react package, which is lightweight and doesn&#39;t include any of the actual rendering logic. To start, we expect people to render DOM-based components with our react-dom package, but there&#39;s nothing stopping someone from diving deep on performance and writing a awesome-faster-react-dom package which can render the exact same DOM-based components. By decoupling the component definitions from the rendering, this becomes possible.More importantly, this paves the way to writing components that can be shared between the web version of React and React Native. This isn&#39;t yet easily possible, but we intend to make this easy in a future version so you can share React code between your website and native apps.The addons have moved to separate packages as well: react-addons-clone-with-props, react-addons-create-fragment, react-addons-css-transition-group, react-addons-linked-state-mixin, react-addons-pure-render-mixin, react-addons-shallow-compare, react-addons-transition-group, and react-addons-update, plus ReactDOM.unstable_batchedUpdates in react-dom.For now, please use the same version of react and react-dom in your apps to avoid versioning problems -- but we plan to remove this requirement later. (This release includes the old methods in the react package with a deprecation warning, but they&#39;ll be removed completely in 0.15.)DOM node refs #The other big change we&#39;re making in this release is exposing refs to DOM components as the DOM node itself. That means: we looked at what you can do with a ref to a DOM component and realized that the only useful thing you can do with it is call this.refs.giraffe.getDOMNode() to get the underlying DOM node. In this release, this.refs.giraffe is the actual DOM node.Refs to custom component classes work exactly as before.var Zoo = React.createClass({ render: function() { return ( &lt;div&gt; Giraffe&#39;s name: &lt;input ref=&quot;giraffe&quot; /&gt; &lt;/div&gt; ); }, showName: function() { // Previously: // var input = this.refs.giraffe.getDOMNode(); var input = this.refs.giraffe; alert(input.value); }});This change also applies to the return result of ReactDOM.render when passing a DOM node as the top component. As with refs, this change does not affect custom components (eg. &lt;MyFancyMenu&gt; or &lt;MyContextProvider&gt;), which remain unaffected by this change.Along with this change, we&#39;re also replacing component.getDOMNode() with ReactDOM.findDOMNode(component). The findDOMNode method drills down to find which DOM node was rendered by a component, but it returns its argument when passed a DOM node so it&#39;s safe to call on a DOM component too. We introduced this function quietly in the last release, but now we&#39;re deprecating .getDOMNode() completely: it should be easy to change all existing calls in your code to be ReactDOM.findDOMNode. We also have an automated codemod script to help you with this transition. Note that the findDOMNode calls are unnecessary when you already have a DOM component ref (as in the example above), so you can (and should) skip them in most cases going forward.We hope you&#39;re as excited about this release as we are! Let us know what you think of it.</summary> | |
| +</entry> | |
| +<entry> | |
| +<title>Deprecating JSTransform and react-tools</title> | |
| +<link href="https://facebook.github.io/react/blog/2015/06/12/deprecating-jstransform-and-react-tools.html" rel="alternate" type="text/html" title="Deprecating JSTransform and react-tools" /> | |
| +<published>2015-06-12T00:00:00-07:00</published> | |
| +<updated>2015-06-12T00:00:00-07:00</updated> | |
| +<id>https://facebook.github.io/react/blog/2015/06/12/deprecating-jstransform-and-react-tools</id> | |
| +<content type="html" xml:base="https://facebook.github.io/react/blog/2015/06/12/deprecating-jstransform-and-react-tools.html"><p>Today we&#39;re announcing the deprecation of react-tools and JSTransform.</p> | |
| <p>As many people have noticed already, React and React Native have both switched their respective build systems to make use of <a href="http://babeljs.io/">Babel</a>. This replaced <a href="https://github.com/facebook/jstransform">JSTransform</a>, the source transformation tool that we wrote at Facebook. JSTransform has been really good for us over the past several years, however as the JavaScript language continues to evolve, the architecture we used has begun to show its age. We&#39;ve faced maintenance issues and lagged behind implementing new language features. Last year, Babel (previously 6to5) exploded onto the scene, implementing new features at an amazing pace. Since then it has evolved a solid plugin API, and implemented some of our non-standard language features (JSX and Flow type annotations).</p> | |
| <p>react-tools has always been a very thin wrapper around JSTransform. It has served as a great tool for the community to get up and running, but at this point we&#39;re ready to <a href="https://www.youtube.com/watch?v=moSFlvxnbgk">let it go</a>. We won&#39;t ship a new version for v0.14.</p> | |
| <h2><a class="anchor" name="migrating-to-babel"></a>Migrating to Babel <a class="hash-link" href="#migrating-to-babel">#</a></h2> | |
| <p>Many people in the React and broader JavaScript community have already adopted Babel. It has <a href="http://babeljs.io/docs/setup/">integrations with a number of tools</a>. Depending on your tool, you&#39;ll want to read up on the instructions.</p> | |
| <p>We&#39;ve been working with the Babel team as we started making use of it and we&#39;re confident that it will be the right tool to use with React.</p> | |
| <h2><a class="anchor" name="other-deprecations"></a>Other Deprecations <a class="hash-link" href="#other-deprecations">#</a></h2><h3><a class="anchor" name="esprima-fb"></a>esprima-fb <a class="hash-link" href="#esprima-fb">#</a></h3> | |
| <p>As a result of no longer maintaining JSTransform, we no longer have a need to maintain our Esprima fork (<a href="https://github.com/facebook/esprima/">esprima-fb</a>). The upstream Esprima and other esprima-based forks, like Espree, have been doing an excellent job of supporting new language features recently. If you have a need of an esprima-based parser, we encourage you to look into using one of those.</p> | |
| <p>Alternatively, if you need to parse JSX, take a look at <a href="https://github.com/marijnh/acorn">acorn</a> parser in combination with <a href="https://github.com/RReverser/acorn-jsx">acorn-jsx</a> plugin which is used inside of Babel and thus always supports the latest syntax.</p> | |
| <h3><a class="anchor" name="jsxtransformer"></a>JSXTransformer <a class="hash-link" href="#jsxtransformer">#</a></h3> | |
| <p>JSXTransformer is another tool we built specifically for consuming JSX in the browser. It was always intended as a quick way to prototype code before setting up a build process. It would look for <code>&lt;script&gt;</code> tags with <code>type=&quot;text/jsx&quot;</code> and then transform and run. This ran the same code that react-tools ran on the server. Babel ships with <a href="https://babeljs.io/docs/usage/browser/">a nearly identical tool</a>, which has already been integrated into <a href="https://jsbin.com/">JS Bin</a>.</p> | |
| <p>We&#39;ll be deprecating JSXTransformer, however the current version will still be available from various CDNs and Bower.</p> | |
| -</description> | |
| - <pubDate>2015-06-12T00:00:00-07:00</pubDate> | |
| - <link>https://facebook.github.io/react/blog/2015/06/12/deprecating-jstransform-and-react-tools.html</link> | |
| - <guid isPermaLink="true">https://facebook.github.io/react/blog/2015/06/12/deprecating-jstransform-and-react-tools.html</guid> | |
| - </item> | |
| - | |
| - <item> | |
| - <title>React Native Release Process</title> | |
| - <description><p>The React Native release process have been a bit chaotic since we open sourced. It was unclear when new code was released, there was no changelog, we bumped the minor and patch version inconsistently and we often had to submit updates right after a release to fix a bad bug. In order to <em>move fast with stable infra</em>, we are introducing a real release process with a two-week release schedule.</p> | |
| +</content> | |
| +<author> | |
| +<name>Paul O’Shannessy</name> | |
| +<uri>https://twitter.com/zpao</uri> | |
| +</author> | |
| +<summary>Today we&#39;re announcing the deprecation of react-tools and JSTransform.As many people have noticed already, React and React Native have both switched their respective build systems to make use of Babel. This replaced JSTransform, the source transformation tool that we wrote at Facebook. JSTransform has been really good for us over the past several years, however as the JavaScript language continues to evolve, the architecture we used has begun to show its age. We&#39;ve faced maintenance issues and lagged behind implementing new language features. Last year, Babel (previously 6to5) exploded onto the scene, implementing new features at an amazing pace. Since then it has evolved a solid plugin API, and implemented some of our non-standard language features (JSX and Flow type annotations).react-tools has always been a very thin wrapper around JSTransform. It has served as a great tool for the community to get up and running, but at this point we&#39;re ready to let it go. We won&#39;t ship a new version for v0.14.Migrating to Babel #Many people in the React and broader JavaScript community have already adopted Babel. It has integrations with a number of tools. Depending on your tool, you&#39;ll want to read up on the instructions.We&#39;ve been working with the Babel team as we started making use of it and we&#39;re confident that it will be the right tool to use with React.Other Deprecations #esprima-fb #As a result of no longer maintaining JSTransform, we no longer have a need to maintain our Esprima fork (esprima-fb). The upstream Esprima and other esprima-based forks, like Espree, have been doing an excellent job of supporting new language features recently. If you have a need of an esprima-based parser, we encourage you to look into using one of those.Alternatively, if you need to parse JSX, take a look at acorn parser in combination with acorn-jsx plugin which is used inside of Babel and thus always supports the latest syntax.JSXTransformer #JSXTransformer is another tool we built specifically for consuming JSX in the browser. It was always intended as a quick way to prototype code before setting up a build process. It would look for &lt;script&gt; tags with type=&quot;text/jsx&quot; and then transform and run. This ran the same code that react-tools ran on the server. Babel ships with a nearly identical tool, which has already been integrated into JS Bin.We&#39;ll be deprecating JSXTransformer, however the current version will still be available from various CDNs and Bower.</summary> | |
| +</entry> | |
| +<entry> | |
| +<title>React Native Release Process</title> | |
| +<link href="https://facebook.github.io/react/blog/2015/05/22/react-native-release-process.html" rel="alternate" type="text/html" title="React Native Release Process" /> | |
| +<published>2015-05-22T00:00:00-07:00</published> | |
| +<updated>2015-05-22T00:00:00-07:00</updated> | |
| +<id>https://facebook.github.io/react/blog/2015/05/22/react-native-release-process</id> | |
| +<content type="html" xml:base="https://facebook.github.io/react/blog/2015/05/22/react-native-release-process.html"><p>The React Native release process have been a bit chaotic since we open sourced. It was unclear when new code was released, there was no changelog, we bumped the minor and patch version inconsistently and we often had to submit updates right after a release to fix a bad bug. In order to <em>move fast with stable infra</em>, we are introducing a real release process with a two-week release schedule.</p> | |
| <p>To explain how it works, let me walk you through an example. Today, Friday, we took the current state of master and put it on the 0.5-stable branch. We <a href="https://github.com/facebook/react-native/releases/tag/v0.5.0-rc">published 0.5.0-rc</a>, an RC (Release Candidate) when we cut the branch. For two weeks, we&#39;re going to let it stabilize and only cherry-pick critical bug fixes from master.</p> | |
| <p>Friday in two weeks, we&#39;re going to publish the 0.5.0 release, create the 0.6-stable branch and publish 0.6.0-rc as well.</p> | |
| <p>The release process is synchronized with Facebook&#39;s mobile release process. This means that everything in the open source release is also being shipped as part of all the Facebook apps that use React Native!</p> | |
| <p>You now have three ways to get React Native. You should chose the one you want based on the amount of risk you tolerate:</p> | |
| @@ -326,25 +361,30 @@ | |
| <li><strong>master</strong>: You have updates as soon as they are committed. This is if you want to live on the bleeding edge or want to submit pull requests.</li> | |
| <li><strong>rc</strong>: If you don&#39;t want to update every day and deal with many instabilities but want to have recent updates, this is your best shot.</li> | |
| <li><strong>release</strong>: This is the most stable version we offer. The trade-off is that it contains commits that are up to a month old.</li> | |
| </ul> | |
| <p>If you want more details, I highly recommend this video that explains how Facebook mobile release process works and why it was setup this way.</p> | |
| <iframe width="650" height="300" src="https://www.youtube.com/embed/mOyoTUETmSM" frameborder="0" allowfullscreen></iframe> | |
| -</description> | |
| - <pubDate>2015-05-22T00:00:00-07:00</pubDate> | |
| - <link>https://facebook.github.io/react/blog/2015/05/22/react-native-release-process.html</link> | |
| - <guid isPermaLink="true">https://facebook.github.io/react/blog/2015/05/22/react-native-release-process.html</guid> | |
| - </item> | |
| - | |
| - <item> | |
| - <title>React v0.13.3</title> | |
| - <description><p>Today we&#39;re sharing another patch release in the v0.13 branch. There are only a few small changes, with a couple to address some issues that arose around that undocumented feature so many of you are already using: <code>context</code>. We also improved developer ergonomics just a little bit, making some warnings better.</p> | |
| +</content> | |
| +<author> | |
| +<name>Vjeux</name> | |
| +<uri>https://twitter.com/vjeux</uri> | |
| +</author> | |
| +<summary>The React Native release process have been a bit chaotic since we open sourced. It was unclear when new code was released, there was no changelog, we bumped the minor and patch version inconsistently and we often had to submit updates right after a release to fix a bad bug. In order to move fast with stable infra, we are introducing a real release process with a two-week release schedule.To explain how it works, let me walk you through an example. Today, Friday, we took the current state of master and put it on the 0.5-stable branch. We published 0.5.0-rc, an RC (Release Candidate) when we cut the branch. For two weeks, we&#39;re going to let it stabilize and only cherry-pick critical bug fixes from master.Friday in two weeks, we&#39;re going to publish the 0.5.0 release, create the 0.6-stable branch and publish 0.6.0-rc as well.The release process is synchronized with Facebook&#39;s mobile release process. This means that everything in the open source release is also being shipped as part of all the Facebook apps that use React Native!You now have three ways to get React Native. You should chose the one you want based on the amount of risk you tolerate:master: You have updates as soon as they are committed. This is if you want to live on the bleeding edge or want to submit pull requests.rc: If you don&#39;t want to update every day and deal with many instabilities but want to have recent updates, this is your best shot.release: This is the most stable version we offer. The trade-off is that it contains commits that are up to a month old.If you want more details, I highly recommend this video that explains how Facebook mobile release process works and why it was setup this way.</summary> | |
| +</entry> | |
| +<entry> | |
| +<title>React v0.13.3</title> | |
| +<link href="https://facebook.github.io/react/blog/2015/05/08/react-v0.13.3.html" rel="alternate" type="text/html" title="React v0.13.3" /> | |
| +<published>2015-05-08T00:00:00-07:00</published> | |
| +<updated>2015-05-08T00:00:00-07:00</updated> | |
| +<id>https://facebook.github.io/react/blog/2015/05/08/react-v0.13.3</id> | |
| +<content type="html" xml:base="https://facebook.github.io/react/blog/2015/05/08/react-v0.13.3.html"><p>Today we&#39;re sharing another patch release in the v0.13 branch. There are only a few small changes, with a couple to address some issues that arose around that undocumented feature so many of you are already using: <code>context</code>. We also improved developer ergonomics just a little bit, making some warnings better.</p> | |
| <p>The release is now available for download:</p> | |
| <ul> | |
| <li><strong>React</strong><br> | |
| Dev build with warnings: <a href="https://fb.me/react-0.13.3.js">https://fb.me/react-0.13.3.js</a><br> | |
| Minified build for production: <a href="https://fb.me/react-0.13.3.min.js">https://fb.me/react-0.13.3.min.js</a><br></li> | |
| <li><strong>React with Add-Ons</strong><br> | |
| @@ -367,25 +407,30 @@ | |
| <li>Loosened <code>dangerouslySetInnerHTML</code> restrictions so <code>{__html: undefined}</code> will no longer throw</li> | |
| <li>Fixed extraneous context warning with non-pure <code>getChildContext</code></li> | |
| <li>Ensure <code>replaceState(obj)</code> retains prototype of <code>obj</code></li> | |
| </ul> | |
| <h3><a class="anchor" name="react-with-add-ons"></a>React with Add-ons <a class="hash-link" href="#react-with-add-ons">#</a></h3><h3><a class="anchor" name="bug-fixes"></a>Bug Fixes <a class="hash-link" href="#bug-fixes">#</a></h3> | |
| <ul> | |
| <li>Test Utils: Ensure that shallow rendering works when components define <code>contextTypes</code></li> | |
| </ul> | |
| -</description> | |
| - <pubDate>2015-05-08T00:00:00-07:00</pubDate> | |
| - <link>https://facebook.github.io/react/blog/2015/05/08/react-v0.13.3.html</link> | |
| - <guid isPermaLink="true">https://facebook.github.io/react/blog/2015/05/08/react-v0.13.3.html</guid> | |
| - </item> | |
| - | |
| - <item> | |
| - <title>GraphQL Introduction</title> | |
| - <description><p>At the React.js conference in late January 2015, we revealed our next major technology in the React family: <a href="http://facebook.github.io/react/blog/2015/02/20/introducing-relay-and-graphql.html">Relay</a>. </p> | |
| +</content> | |
| +<author> | |
| +<name>Paul O’Shannessy</name> | |
| +<uri>https://twitter.com/zpao</uri> | |
| +</author> | |
| +<summary>Today we&#39;re sharing another patch release in the v0.13 branch. There are only a few small changes, with a couple to address some issues that arose around that undocumented feature so many of you are already using: context. We also improved developer ergonomics just a little bit, making some warnings better.The release is now available for download:ReactDev build with warnings: https://fb.me/react-0.13.3.jsMinified build for production: https://fb.me/react-0.13.3.min.jsReact with Add-OnsDev build with warnings: https://fb.me/react-with-addons-0.13.3.jsMinified build for production: https://fb.me/react-with-addons-0.13.3.min.jsIn-Browser JSX transformerhttps://fb.me/JSXTransformer-0.13.3.jsWe&#39;ve also published version 0.13.3 of the react and react-tools packages on npm and the react package on bower.Changelog #React Core #New Features #Added clipPath element and attribute for SVGImproved warnings for deprecated methods in plain JS classesBug Fixes #Loosened dangerouslySetInnerHTML restrictions so {__html: undefined} will no longer throwFixed extraneous context warning with non-pure getChildContextEnsure replaceState(obj) retains prototype of objReact with Add-ons #Bug Fixes #Test Utils: Ensure that shallow rendering works when components define contextTypes</summary> | |
| +</entry> | |
| +<entry> | |
| +<title>GraphQL Introduction</title> | |
| +<link href="https://facebook.github.io/react/blog/2015/05/01/graphql-introduction.html" rel="alternate" type="text/html" title="GraphQL Introduction" /> | |
| +<published>2015-05-01T00:00:00-07:00</published> | |
| +<updated>2015-05-01T00:00:00-07:00</updated> | |
| +<id>https://facebook.github.io/react/blog/2015/05/01/graphql-introduction</id> | |
| +<content type="html" xml:base="https://facebook.github.io/react/blog/2015/05/01/graphql-introduction.html"><p>At the React.js conference in late January 2015, we revealed our next major technology in the React family: <a href="http://facebook.github.io/react/blog/2015/02/20/introducing-relay-and-graphql.html">Relay</a>. </p> | |
| <p>Relay is a new way of structuring client applications that co-locates data-fetching requirements and React components. Instead of placing data fetching logic in some other part of the client application – or embedding this logic in a custom endpoint on the server – we instead co-locate a <em>declarative</em> data-fetching specification alongside the React component. The language of this declarative specification is GraphQL.</p> | |
| <p>GraphQL was not invented to enable Relay. In fact, GraphQL predates Relay by nearly three years. It was invented during the move from Facebook&#39;s HTML5-driven mobile applications to purely native applications. It is a query language for graph data that powers the lion&#39;s share of interactions in the Facebook Android and iOS applications. Any user of the native iOS or Android app in the last two years has used an app powered by GraphQL.</p> | |
| <p>We plan to open-source a reference implementation of a GraphQL server and publish a language specification in the coming months. Our goal is to evolve GraphQL to adapt to a wide range of backends, so that projects and companies can use this technology to access their own data. We believe that this is a compelling way to structure servers and to provide powerful abstractions, frameworks and tools – including, but not exclusively, Relay – for product developers.</p> | |
| <h2><a class="anchor" name="what-is-graphql"></a>What is GraphQL? <a class="hash-link" href="#what-is-graphql">#</a></h2> | |
| <p>A GraphQL query is a string interpreted by a server that returns data in a specified format. Here is an example query: </p> | |
| @@ -461,25 +506,30 @@ | |
| <p>We believe that GraphQL represents a novel way of structuring the client-server contract. Servers publish a type system specific to their application, and GraphQL provides a unified language to query data within the constraints of that type system. That language allows product developers to express data requirements in a form natural to them: a declarative and hierarchal one.</p> | |
| <p>This is a liberating platform for product developers. With GraphQL, no more contending with <em>ad hoc</em> endpoints or object retrieval with multiple roundtrips to access server data; instead an elegant, hierarchical, declarative query dispatched to a single endpoint. No more frequent jumps between client and server development environments to do experimentation or to change or create views of existing data; instead experiments are done and new views built within a native, client development environment exclusively. No more shuffling unstructured data from <em>ad hoc</em> endpoints into business objects; instead a powerful, introspective type system that serves as a platform for tool building.</p> | |
| <p>Product developers are free to focus on their client software and requirements while rarely leaving their development environment; they can more confidently support shipped clients as a system evolves; and they are using a protocol designed to operate well within the constraints of mobile applications. Product developers can query for exactly what they want, in the way they think about it, across their entire application&#39;s data model. </p> | |
| <h2><a class="anchor" name="whats-next"></a>What&#39;s next? <a class="hash-link" href="#whats-next">#</a></h2> | |
| <p>Over the coming months, we will share more technical details about GraphQL, including additional language features, tools that support it, and how it is built and used at Facebook. These posts will culminate in a formal specification of GraphQL to guide implementors across various languages and platforms. We also plan on releasing a reference implementation in the summer, in order to provide a basis for custom deployments and a platform for experimentation. We&#39;re incredibly excited to share this system and work with the open source community to improve it.</p> | |
| -</description> | |
| - <pubDate>2015-05-01T00:00:00-07:00</pubDate> | |
| - <link>https://facebook.github.io/react/blog/2015/05/01/graphql-introduction.html</link> | |
| - <guid isPermaLink="true">https://facebook.github.io/react/blog/2015/05/01/graphql-introduction.html</guid> | |
| - </item> | |
| - | |
| - <item> | |
| - <title>React v0.13.2</title> | |
| - <description><p>Yesterday the <a href="/react/blog/2015/04/17/react-native-v0.4.html">React Native team shipped v0.4</a>. Those of us working on the web team just a few feet away couldn&#39;t just be shown up like that so we&#39;re shipping v0.13.2 today as well! This is a bug fix release to address a few things while we continue to work towards v0.14.</p> | |
| +</content> | |
| +<author> | |
| +<name>Nick Schrock</name> | |
| +<uri>https://twitter.com/schrockn</uri> | |
| +</author> | |
| +<summary>At the React.js conference in late January 2015, we revealed our next major technology in the React family: Relay. Relay is a new way of structuring client applications that co-locates data-fetching requirements and React components. Instead of placing data fetching logic in some other part of the client application – or embedding this logic in a custom endpoint on the server – we instead co-locate a declarative data-fetching specification alongside the React component. The language of this declarative specification is GraphQL.GraphQL was not invented to enable Relay. In fact, GraphQL predates Relay by nearly three years. It was invented during the move from Facebook&#39;s HTML5-driven mobile applications to purely native applications. It is a query language for graph data that powers the lion&#39;s share of interactions in the Facebook Android and iOS applications. Any user of the native iOS or Android app in the last two years has used an app powered by GraphQL.We plan to open-source a reference implementation of a GraphQL server and publish a language specification in the coming months. Our goal is to evolve GraphQL to adapt to a wide range of backends, so that projects and companies can use this technology to access their own data. We believe that this is a compelling way to structure servers and to provide powerful abstractions, frameworks and tools – including, but not exclusively, Relay – for product developers.What is GraphQL? #A GraphQL query is a string interpreted by a server that returns data in a specified format. Here is an example query: { user(id: 3500401) { id, name, isViewerFriend, profilePicture(size: 50) { uri, width, height } }}(Note: this syntax is slightly different from previous GraphQL examples. We&#39;ve recently been making improvements to the language.)And here is the response to that query.{ &quot;user&quot; : { &quot;id&quot;: 3500401, &quot;name&quot;: &quot;Jing Chen&quot;, &quot;isViewerFriend&quot;: true, &quot;profilePicture&quot;: { &quot;uri&quot;: &quot;http://someurl.cdn/pic.jpg&quot;, &quot;width&quot;: 50, &quot;height&quot;: 50 } }}We will dig into the syntax and semantics of GraphQL in a later post, but even a simple example shows many of its design principles:Hierarchical: Most product development today involves the creation and manipulation of view hierarchies. To achieve congruence with the structure of these applications, a GraphQL query itself is a hierarchical set of fields. The query is shaped just like the data it returns. It is a natural way for product engineers to describe data requirements.Product-centric: GraphQL is unapologetically driven by the requirements of views and the front-end engineers that write them. We start with their way of thinking and requirements and build the language and runtime necessary to enable that.Client-specified queries: In GraphQL, the specification for queries are encoded in the client rather than the server. These queries are specified at field-level granularity. In the vast majority of applications written without GraphQL, the server determines the data returned in its various scripted endpoints. A GraphQL query, on the other hand, returns exactly what a client asks for and no more.Backwards Compatible: In a world of deployed native mobile applications with no forced upgrades, backwards compatibility is a challenge. Facebook, for example, releases apps on a two week fixed cycle and pledges to maintain those apps for at least two years. This means there are at a minimum 52 versions of our clients per platform querying our servers at any given time. Client-specified queries simplifies managing our backwards compatibility guarantees.Structured, Arbitrary Code: Query languages with field-level granularity have typically queried storage engines directly, such as SQL. GraphQL instead imposes a structure onto a server, and exposes fields that are backed by arbitrary code. This allows for both server-side flexibility and a uniform, powerful API across the entire surface area of an application.Application-Layer Protocol: GraphQL is an application-layer protocol and does not require a particular transport. It is a string that is parsed and interpreted by a server.Strongly-typed: GraphQL is strongly-typed. Given a query, tooling can ensure that the query is both syntactically correct and valid within the GraphQL type system before execution, i.e. at development time, and the server can make certain guarantees about the shape and nature of the response. This makes it easier to build high quality client tools.Introspective: GraphQL is introspective. Clients and tools can query the type system using the GraphQL syntax itself. This is a powerful platform for building tools and client software, such as automatic parsing of incoming data into strongly-typed interfaces. It is especially useful in statically typed languages such as Swift, Objective-C and Java, as it obviates the need for repetitive and error-prone code to shuffle raw, untyped JSON into strongly-typed business objects.Why invent something new? #Obviously GraphQL is not the first system to manage client-server interactions. In today&#39;s world there are two dominant architectural styles for client-server interaction: REST and ad hoc endpoints. REST #REST, an acronym for Representational State Transfer, is an architectural style rather than a formal protocol. There is actually much debate about what exactly REST is and is not. We wish to avoid such debates. We are interested in the typical attributes of systems that self-identify as REST, rather than systems which are formally REST.Objects in a typical REST system are addressable by URI and interacted with using verbs in the HTTP protocol. An HTTP GET to a particular URI fetches an object and returns a server-specified set of fields. An HTTP PUT edits an object; an HTTP DELETE deletes an object; and so on.We believe there are a number of weakness in typical REST systems, ones that are particularly problematic in mobile applications:Fetching complicated object graphs require multiple round trips between the client and server to render single views. For mobile applications operating in variable network conditions, these multiple roundtrips are highly undesirable.Invariably fields and additional data are added to REST endpoints as the system requirements change. However, old clients also receive this additional data as well, because the data fetching specification is encoded on the server rather than the client. As result, these payloads tend to grow over time for all clients. When this becomes a problem for a system, one solution is to overlay a versioning system onto the REST endpoints. Versioning also complicates a server, and results in code duplication, spaghetti code, or a sophisticated, hand-rolled infrastructure to manage it. Another solution to limit over-fetching is to provide multiple views – such as “compact” vs “full” – of the same REST endpoint, however this coarse granularity often does not offer adequate flexibility.REST endpoints are usually weakly-typed and lack machine-readable metadata. While there is much debate about the merits of strong- versus weak-typing in distributed systems, we believe in strong typing because of the correctness guarantees and tooling opportunities it provides. Developer deal with systems that lack this metadata by inspecting frequently out-of-date documentation and then writing code against the documentation.Many of these attributes are linked to the fact that “REST is intended for long-lived network-based applications that span multiple organizations” according to its inventor. This is not a requirement for APIs that serve a client app built within the same organization.Nearly all externally facing REST APIs we know of trend or end up in these non-ideal states, as well as nearly all internal REST APIs. The consequences of opaqueness and over-fetching are more severe in internal APIs since their velocity of change and level of usage is almost always higher.Because of multiple round-trips and over-fetching, applications built in the REST style inevitably end up building ad hoc endpoints that are superficially in the REST style. These actually couple the data to a particular view which explicitly violates one of REST&#39;s major goals. Most REST systems of any complexity end up as a continuum of endpoints that span from “traditional” REST to ad hoc endpoints.Ad Hoc Endpoints #Many applications have no formalized client-server contract. Product developers access server capabilities through ad hoc endpoints and write custom code to fetch the data they need. Servers define procedures, and they return data. This approach has the virtue of simplicity, but can often become untenable as systems age.These systems typically define a custom endpoint per view. For systems with a wide surface area this can quickly grow into a maintenance nightmare of orphaned endpoints, inconsistent tooling, and massive server code duplication. Disciplined engineering organizations can mitigate these issues with great engineering practices, high quality abstractions, and custom tooling. However, given our experience we believe that custom endpoints tend to lead to entropic server codebases.Much like REST, the payloads of custom endpoints grow monotonically (even with mitigation from versioning systems) as the server evolves. Deployed clients cannot break, and, with rapid release cycles and backwards compatibility guarantees, distributed applications will have large numbers of extant versions. Under these constraints it is difficult remove data from a custom endpoint.Custom endpoints tend to – for a client developer – create a clunky, multi-language, multi-environment development process. No matter if the data has been accessed before in a different view, they are required to first change the custom endpoint, then deploy that code to a server accessible from a mobile device, and only then change the client to utilize that data. In GraphQL – unless the data in the view is completely new to the entire system – a product developer adds a field to a GraphQL query and the work on the client continues unabated.Much like REST, most systems with custom endpoints do not have a formalized type system, which eliminates the possibility for the tools and guarantees that introspective type systems can provide. Some custom-endpoint-driven systems do use a strongly typed serialization scheme, such as Protocol Buffers, Thrift, or XML. Those do allow for direct parsing of responses into typed classes and eliminating boilerplate shuffling from JSON into handwritten classes. These systems are as not as expressive and flexible as GraphQL, and the other downsides of ad hoc endpoints remain.We believe that GraphQL represents a novel way of structuring the client-server contract. Servers publish a type system specific to their application, and GraphQL provides a unified language to query data within the constraints of that type system. That language allows product developers to express data requirements in a form natural to them: a declarative and hierarchal one.This is a liberating platform for product developers. With GraphQL, no more contending with ad hoc endpoints or object retrieval with multiple roundtrips to access server data; instead an elegant, hierarchical, declarative query dispatched to a single endpoint. No more frequent jumps between client and server development environments to do experimentation or to change or create views of existing data; instead experiments are done and new views built within a native, client development environment exclusively. No more shuffling unstructured data from ad hoc endpoints into business objects; instead a powerful, introspective type system that serves as a platform for tool building.Product developers are free to focus on their client software and requirements while rarely leaving their development environment; they can more confidently support shipped clients as a system evolves; and they are using a protocol designed to operate well within the constraints of mobile applications. Product developers can query for exactly what they want, in the way they think about it, across their entire application&#39;s data model. What&#39;s next? #Over the coming months, we will share more technical details about GraphQL, including additional language features, tools that support it, and how it is built and used at Facebook. These posts will culminate in a formal specification of GraphQL to guide implementors across various languages and platforms. We also plan on releasing a reference implementation in the summer, in order to provide a basis for custom deployments and a platform for experimentation. We&#39;re incredibly excited to share this system and work with the open source community to improve it.</summary> | |
| +</entry> | |
| +<entry> | |
| +<title>React v0.13.2</title> | |
| +<link href="https://facebook.github.io/react/blog/2015/04/18/react-v0.13.2.html" rel="alternate" type="text/html" title="React v0.13.2" /> | |
| +<published>2015-04-18T00:00:00-07:00</published> | |
| +<updated>2015-04-18T00:00:00-07:00</updated> | |
| +<id>https://facebook.github.io/react/blog/2015/04/18/react-v0.13.2</id> | |
| +<content type="html" xml:base="https://facebook.github.io/react/blog/2015/04/18/react-v0.13.2.html"><p>Yesterday the <a href="/react/blog/2015/04/17/react-native-v0.4.html">React Native team shipped v0.4</a>. Those of us working on the web team just a few feet away couldn&#39;t just be shown up like that so we&#39;re shipping v0.13.2 today as well! This is a bug fix release to address a few things while we continue to work towards v0.14.</p> | |
| <p>The release is now available for download:</p> | |
| <ul> | |
| <li><strong>React</strong><br> | |
| Dev build with warnings: <a href="https://fb.me/react-0.13.2.js">https://fb.me/react-0.13.2.js</a><br> | |
| Minified build for production: <a href="https://fb.me/react-0.13.2.min.js">https://fb.me/react-0.13.2.min.js</a><br></li> | |
| <li><strong>React with Add-Ons</strong><br> | |
| @@ -513,16 +563,16 @@ | |
| <h3><a class="anchor" name="react-with-add-ons"></a>React with Add-Ons <a class="hash-link" href="#react-with-add-ons">#</a></h3><h4><a class="anchor" name="bug-fixes"></a>Bug Fixes <a class="hash-link" href="#bug-fixes">#</a></h4> | |
| <ul> | |
| <li>Immutabilty Helpers: Ensure it supports <code>hasOwnProperty</code> as an object key</li> | |
| </ul> | |
| <h3><a class="anchor" name="react-tools"></a>React Tools <a class="hash-link" href="#react-tools">#</a></h3> | |
| <ul> | |
| <li>Improve documentation for new options</li> | |
| </ul> | |
| -</description> | |
| - <pubDate>2015-04-18T00:00:00-07:00</pubDate> | |
| - <link>https://facebook.github.io/react/blog/2015/04/18/react-v0.13.2.html</link> | |
| - <guid isPermaLink="true">https://facebook.github.io/react/blog/2015/04/18/react-v0.13.2.html</guid> | |
| - </item> | |
| - | |
| - </channel> | |
| -</rss> | |
| +</content> | |
| +<author> | |
| +<name>Paul O’Shannessy</name> | |
| +<uri>https://twitter.com/zpao</uri> | |
| +</author> | |
| +<summary>Yesterday the React Native team shipped v0.4. Those of us working on the web team just a few feet away couldn&#39;t just be shown up like that so we&#39;re shipping v0.13.2 today as well! This is a bug fix release to address a few things while we continue to work towards v0.14.The release is now available for download:ReactDev build with warnings: https://fb.me/react-0.13.2.jsMinified build for production: https://fb.me/react-0.13.2.min.jsReact with Add-OnsDev build with warnings: https://fb.me/react-with-addons-0.13.2.jsMinified build for production: https://fb.me/react-with-addons-0.13.2.min.jsIn-Browser JSX transformerhttps://fb.me/JSXTransformer-0.13.2.jsWe&#39;ve also published version 0.13.2 of the react and react-tools packages on npm and the react package on bower.Changelog #React Core #New Features #Added strokeDashoffset, flexPositive, flexNegative to the list of unitless CSS propertiesAdded support for more DOM properties:scoped - for &lt;style&gt; elementshigh, low, optimum - for &lt;meter&gt; elementsunselectable - IE-specific property to prevent user selectionBug Fixes #Fixed a case where re-rendering after rendering null didn&#39;t properly pass contextFixed a case where re-rendering after rendering with style={null} didn&#39;t properly update styleUpdate uglify dependency to prevent a bug in IE8Improved warningsReact with Add-Ons #Bug Fixes #Immutabilty Helpers: Ensure it supports hasOwnProperty as an object keyReact Tools #Improve documentation for new options</summary> | |
| +</entry> | |
| +</feed> |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment