From d78b121c39c03c7fae0353ec2b93cde77ef7a0d8 Mon Sep 17 00:00:00 2001 From: John Larsen Date: Thu, 15 Oct 2020 10:58:52 +0100 Subject: [PATCH] Fix backport typo from 16.14.10 to 16.14.0 (#3334) --- content/blog/2020-09-22-introducing-the-new-jsx-transform.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/blog/2020-09-22-introducing-the-new-jsx-transform.md b/content/blog/2020-09-22-introducing-the-new-jsx-transform.md index dee93c74..dd1e3f9e 100644 --- a/content/blog/2020-09-22-introducing-the-new-jsx-transform.md +++ b/content/blog/2020-09-22-introducing-the-new-jsx-transform.md @@ -20,7 +20,7 @@ Upgrading to the new transform is completely optional, but it has a few benefits **This upgrade will not change the JSX syntax and is not required.** The old JSX transform will keep working as usual, and there are no plans to remove the support for it. -[React 17 RC](/blog/2020/08/10/react-v17-rc.html) already includes support for the new transform, so go give it a try! To make it easier to adopt, **we've also backported its support** to React 16.14.10, React 15.7.0, and React 0.14.10. You can find the upgrade instructions for different tools [below](#how-to-upgrade-to-the-new-jsx-transform). +[React 17 RC](/blog/2020/08/10/react-v17-rc.html) already includes support for the new transform, so go give it a try! To make it easier to adopt, **we've also backported its support** to React 16.14.0, React 15.7.0, and React 0.14.10. You can find the upgrade instructions for different tools [below](#how-to-upgrade-to-the-new-jsx-transform). Now let's take a closer look at the differences between the old and the new transform.