s/parse/parser in jstransform deprecation blog post
Dustan Kasten committed
Jun 12, 2015 at 23:57 UTC
54e77a251c4e5309b84c5b76ade5453f2da4afbd
1 file changed
+1
-1
docs/_posts/2015-06-12-deprecating-jstransform-and-react-tools.md
+1
-1
@@ -19,7 +19,7 @@ We've been working with the Babel team as we started making use of it and we're
19
20
### esprima-fb
21
22
-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.
22
+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.
23
24
### JSXTransformer
25
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 `<script>` tags with `type="text/jsx"` and then transform and run. This ran the same code that react-tools ran on the server. Babel ships with [a nearly identical tool](https://babeljs.io/docs/usage/browser/), which has already been integrated into [JS Bin](https://jsbin.com/).