How to Structure React Projects
reactjsnews.com
How to Structure React Projects
1–10 of 45 posts
Re: How to Structure React Projects
#2One of the most confusing things with React and Angular or in fact any other non convention-over-configuration framework is how you go about building your project.
Structure is super important, and this resource looks good.
I would add a demo application on Github that does handle data (something super simple will suffice), just so people can fork the project and take it from there.
I know for me, when I started with Angular, the Yeoman generators were just life savers, I think it would be a great "next stage" for this post.
Re: How to Structure React Projects
#3This is great! One of the most confusing things with React and Angular or in fact any other non convention-over-configuration framework is how you go about building your project. Structure is super important, and this resource looks good. I would add a demo application on Github that does handle data (something super simple will suffice), just so people can fork the project and take it from there. I know for me, when…
Re: How to Structure React Projects
#4It has:
* react-hot-loader which causes your changed to get automatically loaded into the running webpage
* Webpack, gulp and redux all set up
* A sample api server integrated in the development process to be used with a SPA
* SASS/CSS loading, which also gets hot loaded into your page (once/if my pull request is merged)
* Production builds with minifying and no sourcemaps (once/if my pull request is merged)
I'm not entirely happy with the structuring, but that can always be changed once you're familiar with the technologies. I also just submitted pull requests to address the issues listed in the readme.
Re: How to Structure React Projects
#5[1] https://github.com/MadeInHaus/react-flux-gulp-starter [2] https://github.com/kriasoft/react-starter-kit
Re: How to Structure React Projects
#6In my experience, this structure scales very well, especially if you take the advice in the 'thinking in react' tutorial (http://facebook.github.io/react/docs/thinking-in-react.html ) and create a mockup that clearly indicates what part of the UI will be handled with what component.
Re: How to Structure React Projects
#7Re: How to Structure React Projects
#8How is a "component" different from a "view"?
Re: How to Structure React Projects
#9How is a "component" different from a "view"?
Components are "dumb", and just consume props. Views are top level Components, usually rendered by the router, that tie into your fluxy goodness.
Re: How to Structure React Projects
#101. https://github.com/gaearon/redux-devtools/tree/master/exampl...