From be082c9df72a947e2fff8ed2fb7497297b4dd9b2 Mon Sep 17 00:00:00 2001 From: jxom Date: Sun, 8 Oct 2017 00:08:39 +1100 Subject: [PATCH] Modify v16 blog post to elaborate on upgrading via codemods --- content/blog/2017-09-26-react-v16.0.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/blog/2017-09-26-react-v16.0.md b/content/blog/2017-09-26-react-v16.0.md index 9636e8f3..ab8a095b 100644 --- a/content/blog/2017-09-26-react-v16.0.md +++ b/content/blog/2017-09-26-react-v16.0.md @@ -132,7 +132,7 @@ Refer to the documentation for [detailed installation instructions](/docs/instal ## Upgrading -Although React 16 includes significant internal changes, in terms of upgrading, you can think of this like any other major React release. We've been serving React 16 to Facebook and Messenger.com users since earlier this year, and we released several beta and release candidate versions to flush out additional issues. With minor exceptions, **if your app runs in 15.6 without any warnings, it should work in 16.** +Although React 16 includes significant internal changes, in terms of upgrading, you can think of this like any other major React release. We've been serving React 16 to Facebook and Messenger.com users since earlier this year, and we released several beta and release candidate versions to flush out additional issues. For such deprecations listed in [packaging](#packaging) below, a codemod can be run to convert your deprecated code (see [15.5.0](https://reactjs.org/blog/2017/04/07/react-v15.5.0.html) blog post for more information). Otherwise, **if your app runs in 15.6 without any warnings, it should work in 16.** ### New deprecations