{"action":"created","issue":{"url":"https://api.github.com/repos/reactjs/react-rails/issues/310","labels_url":"https://api.github.com/repos/reactjs/react-rails/issues/310/labels{/name}","comments_url":"https://api.github.com/repos/reactjs/react-rails/issues/310/comments","events_url":"https://api.github.com/repos/reactjs/react-rails/issues/310/events","html_url":"https://github.com/reactjs/react-rails/issues/310","id":92300277,"number":310,"title":"Separate react-rails into two gems?","user":{"login":"justin808","id":1118459,"avatar_url":"https://avatars.githubusercontent.com/u/1118459?v=3","gravatar_id":"","url":"https://api.github.com/users/justin808","html_url":"https://github.com/justin808","followers_url":"https://api.github.com/users/justin808/followers","following_url":"https://api.github.com/users/justin808/following{/other_user}","gists_url":"https://api.github.com/users/justin808/gists{/gist_id}","starred_url":"https://api.github.com/users/justin808/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/justin808/subscriptions","organizations_url":"https://api.github.com/users/justin808/orgs","repos_url":"https://api.github.com/users/justin808/repos","events_url":"https://api.github.com/users/justin808/events{/privacy}","received_events_url":"https://api.github.com/users/justin808/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":7,"created_at":"2015-07-01T07:29:12Z","updated_at":"2015-09-22T04:51:31Z","closed_at":null,"body":"@rmosolgo Any opinion if we could or should break react-rails up into two gems? I see the gem as 2 major parts:\r\n\r\n1. The view helpers and corresponding parts that support server side rendering\r\n2. Sprockets integration so that it's super easy to include react and JSX into a Rails project. This gem could include part 1) as a dependency, as well as the [react-source](https://github.com/reactjs/react-rails/blob/master/VERSIONS.md) gem.\r\n\r\nFor those that use these systems below, it would be nice not include the parts related to 2).\r\n\r\nWebpack: https://github.com/justin808/react-webpack-rails-tutorial\r\n\r\nbrowserify-rails: https://github.com/browserify-rails/browserify-rails\r\n\r\n\r\n"},"comment":{"url":"https://api.github.com/repos/reactjs/react-rails/issues/comments/142181254","html_url":"https://github.com/reactjs/react-rails/issues/310#issuecomment-142181254","issue_url":"https://api.github.com/repos/reactjs/react-rails/issues/310","id":142181254,"user":{"login":"justin808","id":1118459,"avatar_url":"https://avatars.githubusercontent.com/u/1118459?v=3","gravatar_id":"","url":"https://api.github.com/users/justin808","html_url":"https://github.com/justin808","followers_url":"https://api.github.com/users/justin808/followers","following_url":"https://api.github.com/users/justin808/following{/other_user}","gists_url":"https://api.github.com/users/justin808/gists{/gist_id}","starred_url":"https://api.github.com/users/justin808/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/justin808/subscriptions","organizations_url":"https://api.github.com/users/justin808/orgs","repos_url":"https://api.github.com/users/justin808/repos","events_url":"https://api.github.com/users/justin808/events{/privacy}","received_events_url":"https://api.github.com/users/justin808/received_events","type":"User","site_admin":false},"created_at":"2015-09-22T04:51:31Z","updated_at":"2015-09-22T04:51:31Z","body":"@guzart Why do you want to do that? One of my team members at https://github.com/shakacode/ is @alexfedoseev who wrote up: https://medium.com/@alexfedoseev/isomorphic-react-with-rails-part-i-440754e82a59.\r\n\r\nThere's many advantages to sticking with sprockets, mainly around simplicity, such as:\r\n\r\n1. Using one port for the app so not needing to setup CORS.\r\n2. Let Rails handle image/font fingerprinting for use with sass-rails, and bootstrap-sass.\r\n"}}