Skip to content
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

Get rid of react_on_rails gem? #155

Open
hlcfan opened this issue Sep 23, 2017 · 2 comments

Comments

Projects
None yet
2 participants
@hlcfan
Copy link
Owner

commented Sep 23, 2017

No description provided.

@hlcfan hlcfan changed the title Get rid of react_on_rails gem Get rid of react_on_rails gem? Sep 24, 2017

@southwolf

This comment has been minimized.

Copy link

commented Sep 25, 2017

What is the best practice of using ReactJS with Rails? react-rails, react_on_rails, or webpacker and pure front-end stack?

@hlcfan

This comment has been minimized.

Copy link
Owner Author

commented Sep 25, 2017

I ain't for sure about the "best practice", but I can share some of my experiences :-)

When Pokrex was using react-rails, there's no webpacker yet, all your code will go through babel(transform), sprocket. It's easy to use, you'll just write your "components", but without webpack, npm, it's like dancing in Rails, instead of "in Javascript". Thanks to webpacker, it now looks like a good choice. Later on I switched to react_on_rails, because it provides with webpack, yarn.etc.

Have to say webpacker is awesome, the reason I'm thinking that remove react_on_rails is that webpacker offers what I want and SSR isn't what I want. But if you want SSR, react-rails or react_on_rails might be your choice, I lean to react-rails, it looks a bit simple. If only CSR, webpacker is simple and good option. IMO.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.