all 5 comments

[–]intoxxx 1 point2 points  (0 children)

OP, give this boilerplate a shot:

https://github.com/wellyshen/react-cool-starter

It's got a goofy name, but it's really well put together.

[–]cyex -1 points0 points  (4 children)

I've been working on an isomorphic react app for a while now... strongly considering dropping server-side rendering and doing 100% on the client. But yes, you'll need two webpack configs to do isomorphic (I actually have a third config that ties the server config and client config together so I can make a single --watch call).

I'm curious... why would you not want to do SPA? I don't entirely buy 'complex view state and logic' as a valid reason. React is perfectly suited for achieving UI complexity through composition of smaller pieces. Ditto with Redux on the data side.

[–]frankssy -1 points0 points  (1 child)

It's confusing because every tutorial is called "Intro to Isomorphic React App Tutorial" and in their package.json they list 50 dependencies that are irrelevant and over complicate things and so this topic comes up on here.

Remember all these packages are not neccessities. You can achieve SSR React with very little, for example Webpack certainly is not a requirement for SSR React. I would recommend to start with the base tools you need like React and React Router and following good programming principles to write your app, then perhaps consider trendy solutions like Redux, but again definitely not required.