Use with webpack-dev-middleware? about webpack-isomorphic-tools

[catamphetamine]

Well, you can try to start the dev-server first and see how it goes.

[mattkrick]

Yep, calling the server directly the first time around & then sending it through the .server callback works OK, just wasn't sure if there's a way to set this up as an express middleware or something similar.

[catamphetamine]

to set up webpack-isomorphic-tools as a middleware?
that wouldn't be possible because it's not a middleware, it's a hacking device.

[mattkrick]

Yeah, you're right, I'm just thinking of some way to hook the reading/parsing/assets writing part to webpack right after it's built instead of just checking for it on an interval.

[catamphetamine]

Well, if you find a way to know when its built - then I'll integrate your solution into the project

[smontlouis]

Hey @mattkrick I have the same issue. Can you tell me exactly how did you do it ?

[mattkrick]

@bulby97 I explain it here: https://medium.com/@matt.krick/a-production-ready-realtime-saas-with-webpack-7b11ba2fa5b0#.rwva7ij4n

[smontlouis]

@mattkrick Thank you !!

[catamphetamine]

FYI
I'm posting this in every issue and PR to notify whoever may be interested:
today I've released an alternative helper library called universal-webpack.
It takes a different approach than webpack-ismorphic-tools and instead of hacking Node.js require() calls it just compiles all code with target: 'node' webpack configuration option.
As a result, all Webpack plugins and features are supported.
If you think you might need that here's an example project:
https://github.com/halt-hammerzeit/webpack-react-redux-isomorphic-render-example