Migrating from webpack-hmr, Error: locals[0] does not appear to be a `module`

[gaearon]

Migrating from webpack-hmr, Error: locals[0] does not appear to be a `module`

[miniMofish]

@hiddaorear 亲，开发环境编译没有这个错，线上环境编译时有，这又是什么情况？

[gaearon]

Closing as a duplicate of #5. This just means that for whatever reason you don't really have HMR enabled. Maybe you're using the same Babel configuration on server and client (you shouldn't), or maybe you don't have hot module replacement enabled in Webpack config.

[tomatau]

It was the server HMR, disabling made it work.. although would be nice to use the same .babelrc for the whole universal project in a convenient manner.

[gaearon]

I agree but you probably wouldn't want to use other transforms on the server either.
Too easy to get unintended memory leaks and weird behavior.

[tomatau]

Hmmm - I've been using some:

    "react-require",
    "babel-root-import"

What are your experiences with the memory leaks and weird behaviour?

[gaearon]

Sorry, I didn't mean Babel plugins.

I meant that you probably wouldn't want to use react-transform or any its friends (react-transform-hmr, react-transform-catch-errors, etc) on the server.

[hiddaorear]

Hi, try this:
webpack.config.js:
devServer: {
historyApiFallback: true,
inline: true,
hot: true,
progress: true
}
and package.json:
"scripts": {
"dev": "webpack-dev-server --progress --hot --profile --colors"
}

hot is the key.

[gaearon]

None of this should matter in React Hot Loader 3.
I know React Transform has been a configuration hell; hopefully, this should be solved.
See gaearon/react-hot-boilerplate#61 if you’d like to try it!