Production setup

Is there any suggested setup for production?

In my mind, it would be something like:

app.use(webpackDevMiddleware(compiler, {
    noInfo: true
}));

if (procsss.env.NODE_ENV !== 'production') {
  app.use(webpackHotServerMiddleware(compiler));
} else {
  app.use((req, res) => {
    const stat = require(dist + '/stat.json')
    const server = require(dist + '/server')
    server(stat)(req, res)
  });
}

app.listen(6060, () => {
    console.log('Server started: http://localhost:6060/');
});

[richardscarrott]

I’ve updated the README with production setup docs – https://github.com/60frames/webpack-hot-server-middleware#production-setup

[richardscarrott]

@wuct Okay great – I’m not sure what @SpaceK33z would like to rename options.serverSideRender to but I suggested options.exposeStats although that would mean that here, we’d be abusing the fact it happens to also force it to wait for the compiler to stabilise due to an implementation detail.

I also suggested having webpack-dev-middleware simply always wait for the compiler to stabilise but if that isn’t an option then I’d be tempted to suggest creating two options, options.alwaysWaitUntilStable and options.exposeStats so your goNext function would do something like this:

function goNext() {
    if(!options.exposeStats && !options.alwaysWaitUntilStable) return next();
    ready(function() {
        if (options.exposeStats) {
            res.locals.webpackStats = webpackStats;
        }
        next();
    }, req);
}

If that get’s changed in webpack-dev-middleware then I think it’d be a good idea to update the docs here to reflect that.