migrated workflow to react-transform

[thebigredgeek]

[thebigredgeek]

https://github.com/tj/frontend-boilerplate/issues/44

[mikaa123]

Just to know, could we use the webpack-dev-server with react-transform?

[tj]

but it's so much more code! haha, what are the benefits?

[thebigredgeek]

Yeah it is. There is a lot of boilerplate needed for transform. @mikaa123 you have to use the express middleware IIRC. I looked at doing this with only the dev server about a month ago but no joy. @tj maybe a good case for one of those "high level packages"? React + Webpack + HMR type all in one thing? I agree it's a lot of boilerplate.

[tj]

yea wtf haha seems like a regression in that sense if the old thing is deprecated

[thebigredgeek]

Yeah IDK why they didn't just roll into something easier to work with. A simple tool that abstracts a lot of that away would be nice.

[tracker1]

For anyone interested, here's my work in progress boilerplate for the server portion that supports webpack + react + hmr, with koa. (I also have material-ui, but very little done on the front end)

https://github.com/tracker1/r3k-example/blob/master/server/server.dev.js

YMMV, I'm working on this as time permits, and it may be broken at any given point, currently works (npm run server:dev). I'm running with the current node 5.

[thebigredgeek]

Bump?

[tj]

still have to check it out, I don't have any issues with the old stuff, but it does mention https://github.com/gaearon/react-transform-boilerplate#can-i-use-webpackdevserver-with-this

[thebigredgeek]

Oh shit I totally didn't see that before haha. I'll see if I can hack that out of this PR this weekend

[schickling]

Any update on this @thebigredgeek? Would love to use it :+1:

Edit: I've got react-transform working without an additional devServer.js using webpack-dev-server. This way you can bring down the boilerplate code to a minimum again.