mirror of
https://github.com/facebook/react-native.git
synced 2025-11-01 09:14:26 +00:00
Deploy website
Deploy website version based on 8cd56f37c2d6bcac2fcd4371dfbba95e15996d0a
This commit is contained in:
Website Deployment Script
@@ -87,7 +87,7 @@
|
||||
<ul>
|
||||
<li>Check out the new app screen on the “*<a href="https://www.youtube.com/watch?v=ImlAqMZxveg">React Native Show</a>“ *video series.</li>
|
||||
</ul></li>
|
||||
<li><strong>TurboModule Types:</strong> The new <a href="https://github.com/react-native-community/discussions-and-proposals/issues/40">TurboModules system</a> requires<a href="https://github.com/facebook/react-native/issues/24875">types for all native modules</a> to guarantee type safe operations in native. In just over two weeks, the community sent ~40 Pull Requests to complete this work for flow typed native modules. Aside from the people already mentioned above, we’d like to thank <a href="https://twitter.com/michalchudziak">Michał Chudziak</a>, <a href="https://twitter.com/thymikee">Michał Pierzchała</a>, <a href="https://github.com/wojteg1337">Wojtek Szafraniec</a>, and <a href="https://github.com/jeanregisser">Jean Regisser</a> and everyone else who sent one or more Pull Requests.</li>
|
||||
<li><strong>TurboModule Types:</strong> The new <a href="https://github.com/react-native-community/discussions-and-proposals/issues/40">TurboModules system</a> requires <a href="https://github.com/facebook/react-native/issues/24875">types for all native modules</a> to guarantee type safe operations in native. In just over two weeks, the community sent ~40 Pull Requests to complete this work for flow typed native modules. Aside from the people already mentioned above, we’d like to thank <a href="https://twitter.com/michalchudziak">Michał Chudziak</a>, <a href="https://twitter.com/thymikee">Michał Pierzchała</a>, <a href="https://github.com/wojteg1337">Wojtek Szafraniec</a>, and <a href="https://github.com/jeanregisser">Jean Regisser</a> and everyone else who sent one or more Pull Requests.</li>
|
||||
<li><strong>Haste:</strong> Since 2015 React Native used the <a href="https://github.com/reactjs/reactjs.org/commit/0629e3e2289ed54fac854472aec9a5f6c8318c98#diff-c42b758729cb89976b3a8fd51d1227fa">“haste” module system</a> that allows importing modules just via a global id instead of a relative path which is convenient but not well supported by many tools. <a href="https://twitter.com/JI">James Ide</a> proposed removing haste, similar to how React removed haste many years ago. He planned all the work through an <a href="https://github.com/facebook/react-native/issues/24316">umbrella task</a> and he sent 18 Pull Requests to make it happen! Check out <a href="https://twitter.com/JI/status/1136369775083319296">his Twitter thread</a> to learn more.</li>
|
||||
<li><strong>Android Fragments:</strong> <a href="https://github.com/jpshelley">John Shelley</a>‘s proposal to make React Native work via <a href="https://github.com/facebook/react-native/pull/12199">Android Fragments</a> was merged and will be available in 0.61. <a href="https://developer.android.com/guide/components/fragments">Read more about Android Fragments here</a>.</li>
|
||||
</ul>
|
||||
@@ -114,7 +114,7 @@
|
||||
<p>Given the large amount of changes in the past six months, we'd like to ask you the same question again. If you are using the latest version of React Native and you have things you'd like to give feedback on, please comment on our new edition of <a href="https://github.com/react-native-community/discussions-and-proposals/issues/134">“What do you dislike about React Native?”</a></p>
|
||||
<h2><a class="anchor" aria-hidden="true" id="continuous-integration"></a><a href="#continuous-integration" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Continuous Integration</h2>
|
||||
<p>Facebook merges all Pull Requests and internal changes directly into Facebook’s repository first and then syncs all commits back to GitHub. Facebook’s infrastructure is different from common continuous integration services and not all open source tests were ran inside of Facebook. This means that commits that sync out to GitHub frequently break tests in open source which take a lot of time to fix.</p>
|
||||
<p><a href="https://twitter.com/hectorramos">Héctor Ramos</a> from the React Native team spent the past two months improving React Native's continuous integration systems both at Facebook at on GitHub. Most of the open source tests are now run before changes are committed to React Native at Facebook which will keep CI stable on GitHub when commits are being synchronized.</p>
|
||||
<p><a href="https://twitter.com/hectorramos">Héctor Ramos</a> from the React Native team spent the past two months improving React Native's continuous integration systems both at Facebook and on GitHub. Most of the open source tests are now run before changes are committed to React Native at Facebook which will keep CI stable on GitHub when commits are being synchronized.</p>
|
||||
<h2><a class="anchor" aria-hidden="true" id="next"></a><a href="#next" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Next</h2>
|
||||
<p>Make sure to check out our talks about the future of React Native! In the next couple of months, members of the React Native team at Facebook will speak at <a href="https://infinite.red/ChainReactConf">Chain React</a> and at <a href="https://react-native.eu/">React Native EU</a>. Also, watch out for our next release, 0.60, which is right around the corner. <em>It's going to be exciting</em> ✨</p>
|
||||
</span></div></div><div class="blogSocialSection"><div class="blogSocialSectionItem"><a href="https://twitter.com/share" class="twitter-share-button" data-text="React Native Open Source Update June 2019" data-url="https://facebook.github.io/react-native/blog/2019/06/12/react-native-open-source-update" data-related="reactnative" data-via="cpojer" data-show-count="false">Tweet</a></div><div class="blogSocialSectionItem"><div class="fb-like" data-href="https://facebook.github.io/react-native/blog/2019/06/12/react-native-open-source-update" data-layout="standard" data-share="true" data-width="225" data-show-faces="false"></div></div></div></div><div class="blog-recent"><a class="button" href="/react-native/blog">Recent Posts</a></div></div></div></div><footer class="nav-footer" id="footer"><section class="sitemap"><a href="/react-native/" class="nav-home"><img src="/react-native/img/header_logo.png" alt="React Native" width="66" height="58"/></a><div><h5><a href="/react-native/docs/getting-started.html">Docs</a></h5><a href="/react-native/docs/getting-started.html">Getting Started</a><a href="/react-native/docs/tutorial.html">Tutorial</a><a href="/react-native/docs/components-and-apis.html">Components and APIs</a><a href="/react-native/docs/more-resources.html">More Resources</a></div><div><h5>Community</h5><a href="/react-native/help.html">The React Native Community</a><a href="/react-native/showcase.html">Who's using React Native?</a><a href="http://stackoverflow.com/questions/tagged/react-native" target="_blank">Ask Questions on Stack Overflow</a><a href="https://github.com/facebook/react-native/blob/master/CONTRIBUTING.md">Contributor Guide</a></div><div><h5>More Resources</h5><a href="/react-native/blog/">Blog</a><a href="https://twitter.com/reactnative" target="_blank">Twitter</a><a href="https://github.com/facebook/react-native" target="_blank">GitHub</a><a href="http://reactjs.org" target="_blank">React</a></div></section><a href="https://code.facebook.com/projects/" target="_blank" class="fbOpenSource"><img src="/react-native/img/oss_logo.png" alt="Facebook Open Source" width="170" height="45"/></a><section class="copyright">Copyright © 2019 Facebook Inc.</section></footer></div><script type="text/javascript" src="https://cdn.jsdelivr.net/docsearch.js/1/docsearch.min.js"></script><script>window.fbAsyncInit = function() {FB.init({appId:'1677033832619985',xfbml:true,version:'v2.7'});};(function(d, s, id){var js, fjs = d.getElementsByTagName(s)[0];if (d.getElementById(id)) {return;}js = d.createElement(s); js.id = id;js.src = '//connect.facebook.net/en_US/sdk.js';fjs.parentNode.insertBefore(js, fjs);}(document, 'script','facebook-jssdk'));
|
||||
|
||||
@@ -87,7 +87,7 @@
|
||||
<ul>
|
||||
<li>Check out the new app screen on the “*<a href="https://www.youtube.com/watch?v=ImlAqMZxveg">React Native Show</a>“ *video series.</li>
|
||||
</ul></li>
|
||||
<li><strong>TurboModule Types:</strong> The new <a href="https://github.com/react-native-community/discussions-and-proposals/issues/40">TurboModules system</a> requires<a href="https://github.com/facebook/react-native/issues/24875">types for all native modules</a> to guarantee type safe operations in native. In just over two weeks, the community sent ~40 Pull Requests to complete this work for flow typed native modules. Aside from the people already mentioned above, we’d like to thank <a href="https://twitter.com/michalchudziak">Michał Chudziak</a>, <a href="https://twitter.com/thymikee">Michał Pierzchała</a>, <a href="https://github.com/wojteg1337">Wojtek Szafraniec</a>, and <a href="https://github.com/jeanregisser">Jean Regisser</a> and everyone else who sent one or more Pull Requests.</li>
|
||||
<li><strong>TurboModule Types:</strong> The new <a href="https://github.com/react-native-community/discussions-and-proposals/issues/40">TurboModules system</a> requires <a href="https://github.com/facebook/react-native/issues/24875">types for all native modules</a> to guarantee type safe operations in native. In just over two weeks, the community sent ~40 Pull Requests to complete this work for flow typed native modules. Aside from the people already mentioned above, we’d like to thank <a href="https://twitter.com/michalchudziak">Michał Chudziak</a>, <a href="https://twitter.com/thymikee">Michał Pierzchała</a>, <a href="https://github.com/wojteg1337">Wojtek Szafraniec</a>, and <a href="https://github.com/jeanregisser">Jean Regisser</a> and everyone else who sent one or more Pull Requests.</li>
|
||||
<li><strong>Haste:</strong> Since 2015 React Native used the <a href="https://github.com/reactjs/reactjs.org/commit/0629e3e2289ed54fac854472aec9a5f6c8318c98#diff-c42b758729cb89976b3a8fd51d1227fa">“haste” module system</a> that allows importing modules just via a global id instead of a relative path which is convenient but not well supported by many tools. <a href="https://twitter.com/JI">James Ide</a> proposed removing haste, similar to how React removed haste many years ago. He planned all the work through an <a href="https://github.com/facebook/react-native/issues/24316">umbrella task</a> and he sent 18 Pull Requests to make it happen! Check out <a href="https://twitter.com/JI/status/1136369775083319296">his Twitter thread</a> to learn more.</li>
|
||||
<li><strong>Android Fragments:</strong> <a href="https://github.com/jpshelley">John Shelley</a>‘s proposal to make React Native work via <a href="https://github.com/facebook/react-native/pull/12199">Android Fragments</a> was merged and will be available in 0.61. <a href="https://developer.android.com/guide/components/fragments">Read more about Android Fragments here</a>.</li>
|
||||
</ul>
|
||||
@@ -114,7 +114,7 @@
|
||||
<p>Given the large amount of changes in the past six months, we'd like to ask you the same question again. If you are using the latest version of React Native and you have things you'd like to give feedback on, please comment on our new edition of <a href="https://github.com/react-native-community/discussions-and-proposals/issues/134">“What do you dislike about React Native?”</a></p>
|
||||
<h2><a class="anchor" aria-hidden="true" id="continuous-integration"></a><a href="#continuous-integration" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Continuous Integration</h2>
|
||||
<p>Facebook merges all Pull Requests and internal changes directly into Facebook’s repository first and then syncs all commits back to GitHub. Facebook’s infrastructure is different from common continuous integration services and not all open source tests were ran inside of Facebook. This means that commits that sync out to GitHub frequently break tests in open source which take a lot of time to fix.</p>
|
||||
<p><a href="https://twitter.com/hectorramos">Héctor Ramos</a> from the React Native team spent the past two months improving React Native's continuous integration systems both at Facebook at on GitHub. Most of the open source tests are now run before changes are committed to React Native at Facebook which will keep CI stable on GitHub when commits are being synchronized.</p>
|
||||
<p><a href="https://twitter.com/hectorramos">Héctor Ramos</a> from the React Native team spent the past two months improving React Native's continuous integration systems both at Facebook and on GitHub. Most of the open source tests are now run before changes are committed to React Native at Facebook which will keep CI stable on GitHub when commits are being synchronized.</p>
|
||||
<h2><a class="anchor" aria-hidden="true" id="next"></a><a href="#next" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Next</h2>
|
||||
<p>Make sure to check out our talks about the future of React Native! In the next couple of months, members of the React Native team at Facebook will speak at <a href="https://infinite.red/ChainReactConf">Chain React</a> and at <a href="https://react-native.eu/">React Native EU</a>. Also, watch out for our next release, 0.60, which is right around the corner. <em>It's going to be exciting</em> ✨</p>
|
||||
</span></div></div><div class="blogSocialSection"><div class="blogSocialSectionItem"><a href="https://twitter.com/share" class="twitter-share-button" data-text="React Native Open Source Update June 2019" data-url="https://facebook.github.io/react-native/blog/2019/06/12/react-native-open-source-update" data-related="reactnative" data-via="cpojer" data-show-count="false">Tweet</a></div><div class="blogSocialSectionItem"><div class="fb-like" data-href="https://facebook.github.io/react-native/blog/2019/06/12/react-native-open-source-update" data-layout="standard" data-share="true" data-width="225" data-show-faces="false"></div></div></div></div><div class="blog-recent"><a class="button" href="/react-native/blog">Recent Posts</a></div></div></div></div><footer class="nav-footer" id="footer"><section class="sitemap"><a href="/react-native/" class="nav-home"><img src="/react-native/img/header_logo.png" alt="React Native" width="66" height="58"/></a><div><h5><a href="/react-native/docs/getting-started.html">Docs</a></h5><a href="/react-native/docs/getting-started.html">Getting Started</a><a href="/react-native/docs/tutorial.html">Tutorial</a><a href="/react-native/docs/components-and-apis.html">Components and APIs</a><a href="/react-native/docs/more-resources.html">More Resources</a></div><div><h5>Community</h5><a href="/react-native/help.html">The React Native Community</a><a href="/react-native/showcase.html">Who's using React Native?</a><a href="http://stackoverflow.com/questions/tagged/react-native" target="_blank">Ask Questions on Stack Overflow</a><a href="https://github.com/facebook/react-native/blob/master/CONTRIBUTING.md">Contributor Guide</a></div><div><h5>More Resources</h5><a href="/react-native/blog/">Blog</a><a href="https://twitter.com/reactnative" target="_blank">Twitter</a><a href="https://github.com/facebook/react-native" target="_blank">GitHub</a><a href="http://reactjs.org" target="_blank">React</a></div></section><a href="https://code.facebook.com/projects/" target="_blank" class="fbOpenSource"><img src="/react-native/img/oss_logo.png" alt="Facebook Open Source" width="170" height="45"/></a><section class="copyright">Copyright © 2019 Facebook Inc.</section></footer></div><script type="text/javascript" src="https://cdn.jsdelivr.net/docsearch.js/1/docsearch.min.js"></script><script>window.fbAsyncInit = function() {FB.init({appId:'1677033832619985',xfbml:true,version:'v2.7'});};(function(d, s, id){var js, fjs = d.getElementsByTagName(s)[0];if (d.getElementById(id)) {return;}js = d.createElement(s); js.id = id;js.src = '//connect.facebook.net/en_US/sdk.js';fjs.parentNode.insertBefore(js, fjs);}(document, 'script','facebook-jssdk'));
|
||||
|
||||
+2
-2
@@ -87,7 +87,7 @@
|
||||
<ul>
|
||||
<li>Check out the new app screen on the “*<a href="https://www.youtube.com/watch?v=ImlAqMZxveg">React Native Show</a>“ *video series.</li>
|
||||
</ul></li>
|
||||
<li><strong>TurboModule Types:</strong> The new <a href="https://github.com/react-native-community/discussions-and-proposals/issues/40">TurboModules system</a> requires<a href="https://github.com/facebook/react-native/issues/24875">types for all native modules</a> to guarantee type safe operations in native. In just over two weeks, the community sent ~40 Pull Requests to complete this work for flow typed native modules. Aside from the people already mentioned above, we’d like to thank <a href="https://twitter.com/michalchudziak">Michał Chudziak</a>, <a href="https://twitter.com/thymikee">Michał Pierzchała</a>, <a href="https://github.com/wojteg1337">Wojtek Szafraniec</a>, and <a href="https://github.com/jeanregisser">Jean Regisser</a> and everyone else who sent one or more Pull Requests.</li>
|
||||
<li><strong>TurboModule Types:</strong> The new <a href="https://github.com/react-native-community/discussions-and-proposals/issues/40">TurboModules system</a> requires <a href="https://github.com/facebook/react-native/issues/24875">types for all native modules</a> to guarantee type safe operations in native. In just over two weeks, the community sent ~40 Pull Requests to complete this work for flow typed native modules. Aside from the people already mentioned above, we’d like to thank <a href="https://twitter.com/michalchudziak">Michał Chudziak</a>, <a href="https://twitter.com/thymikee">Michał Pierzchała</a>, <a href="https://github.com/wojteg1337">Wojtek Szafraniec</a>, and <a href="https://github.com/jeanregisser">Jean Regisser</a> and everyone else who sent one or more Pull Requests.</li>
|
||||
<li><strong>Haste:</strong> Since 2015 React Native used the <a href="https://github.com/reactjs/reactjs.org/commit/0629e3e2289ed54fac854472aec9a5f6c8318c98#diff-c42b758729cb89976b3a8fd51d1227fa">“haste” module system</a> that allows importing modules just via a global id instead of a relative path which is convenient but not well supported by many tools. <a href="https://twitter.com/JI">James Ide</a> proposed removing haste, similar to how React removed haste many years ago. He planned all the work through an <a href="https://github.com/facebook/react-native/issues/24316">umbrella task</a> and he sent 18 Pull Requests to make it happen! Check out <a href="https://twitter.com/JI/status/1136369775083319296">his Twitter thread</a> to learn more.</li>
|
||||
<li><strong>Android Fragments:</strong> <a href="https://github.com/jpshelley">John Shelley</a>‘s proposal to make React Native work via <a href="https://github.com/facebook/react-native/pull/12199">Android Fragments</a> was merged and will be available in 0.61. <a href="https://developer.android.com/guide/components/fragments">Read more about Android Fragments here</a>.</li>
|
||||
</ul>
|
||||
@@ -114,7 +114,7 @@
|
||||
<p>Given the large amount of changes in the past six months, we'd like to ask you the same question again. If you are using the latest version of React Native and you have things you'd like to give feedback on, please comment on our new edition of <a href="https://github.com/react-native-community/discussions-and-proposals/issues/134">“What do you dislike about React Native?”</a></p>
|
||||
<h2><a class="anchor" aria-hidden="true" id="continuous-integration"></a><a href="#continuous-integration" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Continuous Integration</h2>
|
||||
<p>Facebook merges all Pull Requests and internal changes directly into Facebook’s repository first and then syncs all commits back to GitHub. Facebook’s infrastructure is different from common continuous integration services and not all open source tests were ran inside of Facebook. This means that commits that sync out to GitHub frequently break tests in open source which take a lot of time to fix.</p>
|
||||
<p><a href="https://twitter.com/hectorramos">Héctor Ramos</a> from the React Native team spent the past two months improving React Native's continuous integration systems both at Facebook at on GitHub. Most of the open source tests are now run before changes are committed to React Native at Facebook which will keep CI stable on GitHub when commits are being synchronized.</p>
|
||||
<p><a href="https://twitter.com/hectorramos">Héctor Ramos</a> from the React Native team spent the past two months improving React Native's continuous integration systems both at Facebook and on GitHub. Most of the open source tests are now run before changes are committed to React Native at Facebook which will keep CI stable on GitHub when commits are being synchronized.</p>
|
||||
<h2><a class="anchor" aria-hidden="true" id="next"></a><a href="#next" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83.42-1.64 1-2.09V6.25c-1.09.53-2 1.84-2 3.25C6 11.31 7.55 13 9 13h4c1.45 0 3-1.69 3-3.5S14.5 6 13 6z"></path></svg></a>Next</h2>
|
||||
<p>Make sure to check out our talks about the future of React Native! In the next couple of months, members of the React Native team at Facebook will speak at <a href="https://infinite.red/ChainReactConf">Chain React</a> and at <a href="https://react-native.eu/">React Native EU</a>. Also, watch out for our next release, 0.60, which is right around the corner. <em>It's going to be exciting</em> ✨</p>
|
||||
</span></div></article></div><div class="post"><header class="postHeader"><h1 class="postHeaderTitle"><a href="/react-native/blog/2019/05/01/react-native-at-f8-and-podcast">React Native at F8 and Open Source Podcast</a></h1><p class="post-meta">May 1, 2019</p><div class="authorBlock"><p class="post-authorName"><a href="https://twitter.com/cpojer" target="_blank" rel="noreferrer noopener">Christoph Nakazawa</a>Engineer at Facebook</p><div class="authorPhoto authorPhotoBig"><a href="https://twitter.com/cpojer" target="_blank" rel="noreferrer noopener"><img src="https://avatars2.githubusercontent.com/u/13352?s=460&v=4" alt="Christoph Nakazawa"/></a></div></div></header><article class="post-content"><div><span><p>This week, <a href="https://twitter.com/Eli_White">Eli White</a> gave a talk at <a href="https://developers.facebook.com/videos/2019/mobile-innovation-with-react-native-componentkit-and-litho/">F8 2019</a> about React Native in Facebook's Android and iOS applications. We are excited to share what we've been up to for the past two years and what we're doing next.</p>
|
||||
|
||||
Reference in New Issue
Block a user