-
Notifications
You must be signed in to change notification settings - Fork 755
Use Babel to transform JS #292
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Sounds good, it should be a pretty straight-forward swap.
Any takers out there?? :) |
I can give it a try On Wednesday, June 10, 2015, Robert Mosolgo [email protected]
Vipul A.M. |
vipulnsward
added a commit
to vipulnsward/react-rails
that referenced
this issue
Jun 11, 2015
… ruby-babel-transpiler - Make new BabelTransformer the default transformer - README changes to reflect new Babel Transformer - Added deprecation warning for usage of old transformer options - Move old transformer to JSXTransformer - Fixed component generator test after changes to new transformer Fixes reactjs#292, reactjs#278
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
We're going to deprecate JSXTransformer and probably not ship any more versions of it. We've already switched the React build process to use Babel and we're going to encourage others to as well. It would make sense for react-rails to follow suit. It would also fix issues like #278.
The
babel-transpiler
gem looks like it should be pretty easy to drop in. https://github.com/babel/ruby-babel-transpilerThe text was updated successfully, but these errors were encountered: