From f195b7f837f432e86a531ccb2e0798a9d03632e0 Mon Sep 17 00:00:00 2001 From: Dustan Kasten Date: Fri, 12 Jun 2015 23:57:49 -0400 Subject: [PATCH] s/parse/parser in jstransform deprecation blog post --- _posts/2015-06-12-deprecating-jstransform-and-react-tools.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/_posts/2015-06-12-deprecating-jstransform-and-react-tools.md b/_posts/2015-06-12-deprecating-jstransform-and-react-tools.md index c8bf0f12..0f0c074d 100644 --- a/_posts/2015-06-12-deprecating-jstransform-and-react-tools.md +++ b/_posts/2015-06-12-deprecating-jstransform-and-react-tools.md @@ -19,7 +19,7 @@ We've been working with the Babel team as we started making use of it and we're ### esprima-fb -As a result of no longer maintaining JSTransform, we no longer have a need to maintain our Esprima fork ([esprima-fb](https://github.com/facebook/esprima/)). 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 parse, we encourage you to look into using one of those. +As a result of no longer maintaining JSTransform, we no longer have a need to maintain our Esprima fork ([esprima-fb](https://github.com/facebook/esprima/)). 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. ### 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 `