-
Notifications
You must be signed in to change notification settings - Fork 47.3k
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
Examples on workflows #2501
Examples on workflows #2501
Conversation
I have written a few articles on setting up a workflow with React JS, [Choosing the correct packaging tool for React JS](http://christianalfoni.github.io/javascript/2014/08/29/choosing-the-correct-packaging-tool-for-react-js.html#comment-1688477691), [React JS and a browserify workflow](http://christianalfoni.github.io/javascript/2014/08/15/react-js-workflow.html) and [React JS and a browserify workflow, PART 2[(http://christianalfoni.github.io/javascript/2014/10/30/react-js-workflow-part2.html). Based on the feedback developers are in dire need for a good workflow. I ran a suggestion on this as an issue, but there has not been an update to the website, so I thought I would try to go more "hands on" with it :-) Thanks for sharing React JS with the community!
There are so many |
I think pointing to actual packages working with various module systems would be more useful than blog posts, as they provide examples on how to be implemented with the system the user choses |
Hi, @bloodyowl The pull request is a link to a boilerplate with Browserify, I mentioned the blog posts only in the pull request to point out what the problem is :-) @zigomir I see your point, but the community is having problems even getting going with React JS. There are no best practices on what tools to combine it with to actually build a web application. Nothing about how to use it in your workflow. Not even how to set up a test environment. It is extremely frustrating. It is not very nice to create something this awesome and push people on a google search hunt for several days before they have something that works for them ;-) This is based on my own experience and the feedback I have gotten. I did not want my example boilerplate to be the only example in the official docs, I want Facebook to officially start sharing practices with the community, something that would hopefully evolve into best practices at some point. Maybe I am being a drama queen about this, but it can not possibly hurt the community to give them more information on how to use React JS? |
We're not going to suggest any specific tools there in the docs at this point. We do refer to the wiki page which has a lot of related packages, I suggest adding yours there. https://github.com/facebook/react/wiki/Complementary-Tools We may want to link to the wiki from where you're editing though. I'd be happy to take that PR but not this one. Thanks for taking the time to write this up (and of course for making the package)! |
Ah, that is great @zpao! I think a lot of people start with that exact page, so it is a great place to give people a "map" of whats out there :-) I will get right on it! |
Based on conversation in facebook#2501. A good place to guide people further in finding the complete set of tools needed to build an application.
I have written a few articles on setting up a workflow with React JS, Choosing the correct packaging tool for React JS, React JS and a browserify workflow and [React JS and a browserify workflow, PART 2[(http://christianalfoni.github.io/javascript/2014/10/30/react-js-workflow-part2.html). Based on the feedback developers are in dire need for a good workflow. I ran a suggestion on this as an issue, but there has not been an update to the website, so I thought I would try to go more "hands on" with it :-)
Thanks for sharing React JS with the community!