Comment by mxstbr | Hacker News Reader

Comment by mxstbr | Hacker News Reader

Hey everybody,

I'm the main contributor behind this boilerplate. I'm currently hard at work getting v3 out, which you can see in the v3.0.0[0] branch of the repo.

The biggest changes are: A new application structure to keep most of the webpack magic hidden from users, stateless components across the board, a npm run pagespeed command and much better documentation.

This was posted while I was sleeping (thanks tilt!), so I'll go through this thread to answer any questions/concerns. If you can think of any more questions you have, reply to this comment so I get a notification!

Cheers!

Minor Edit: You can also follow me on twitter[1] under the same handle stay up to date with changes to the boilerplate!

[0]: https://github.com/mxstbr/react-boilerplate/tree/v3.0.0 [1]: https://twitter.com/mxstbr

Is your webpack config compatible with Windows? Most of them set environment variables in a way that is not cross platform.

I honestly haven't tried it, that's a very very good point.

How would I set them so it works on Windows as well? I'll change it asap!

If you want to do Windows, consider using https://github.com/kentcdodds/argv-set-env for a cross-platform solution to setting enviroment variables

Thanks, it's now fixed for the master branch using kentcdodds/cross-env.[0]

[0]: See this commit: https://github.com/mxstbr/react-boilerplate/commit/ea5794333...

Why did you decide not to use Immutable(JS or other) as part of the boilerplate?

This is something I've been thinking about recently, I decided that for smaller projects having ImmutableJS included isn't very helpful. It's a lot of code overhead for not that much benefit.

Instead I Object.freeze the state[0], so developers get a warning when they mutate the state directly.

I'm happy to change this though, what do you see as the main benefits of including Immutable(JS or other)?

[0]: https://github.com/mxstbr/react-boilerplate/blob/master/js/r...

Looks like the boilerplate here is ground work for large projects.

Generally Immutable makes the reducers syntax much cleaner and allows to more easily "query" the state.

I am myself torn between using it and thus asked..

I opened an issue in the react-boilerplate repo, feel free to jump in and add your two cents: https://github.com/mxstbr/react-boilerplate/issues/46

Reply on news.ycombinator.com