On January, webpack4 was pre-released as beta.0.
On February 25, webpack4 was released 🎉
Webpack4 doesn't need a config file by default!
It made me...
For further actions, you may consider blocking this person and/or reporting abuse
webpack-dev-middleware + webpack-dev-server +
server.js:
...
app.use(webpackDevMiddleware(compiler, {
publicPath: config.output.publicPath
}));
...
webpack.config.js:
...
new webpack.DefinePlugin({'process.env.NODE_ENV': JSON.stringify(process.env.NODE_ENV)}),
or as u did mention
new webpack.DefinePlugin({'process.env.NODE_ENV': JSON.stringify('production')}),
...
Gives me:
WARNING in configuration
The 'mode' option has not been set. Set 'mode' option to 'development' or 'production' to enable defaults for this environment.
package.json:
...
"webpack": "4.0.1",
"webpack-cli": "2.0.9"
"webpack-dev-middleware": "3.0.0",
"webpack-dev-server": "3.1.0",
...
it seems most latest versions...
How to set 'mode' while using webpack-dev-middleware + webpack-dev-server, any suggestions? ;)
p.s. webpack via command line works fine ;)
Sorry to reply late.
If your webpack.config.js doesn't have 'mode' property, you have to add 'mode' property into your webpack.config.js.
The below is an example.
Thank you for reading this post.
Hello, Masashi Hirano.
It's seems im miss something in the past, here is examples ) github.com/webpack/webpack/tree/ma...
Anyway, thx ) for response.