OSX 10.14.6v14.15.16.14.85.9.0v4.0.0-beta.0
checkout repo: [email protected]:sprilukin/webpack-dev-server-beta4-proxy-issue.git
or use these code snippets:
// webpack.config.js
module.exports = [
{
entry: {
'entry1': './src/entry1'
},
devServer: {
proxy: {
'*': {
target: "http://localhost:8080",
bypass: function (req) {
return req.url;
}
}
}
}
},
{
entry: {
'entry2': './src/entry2'
}
}
];
// ./src/entry1
console.log("Entry 1");
// ./src/entry2
console.log("Entry 2");
dev server started successfully
There is an error in the console during starting dev server:
(node:8289) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'level' of undefined
at /Users/sergey/work/my/js/webpack-dev-server-proxy-issue/node_modules/webpack-dev-server/lib/Server.js:203:57
at Array.map (<anonymous>)
at Server.setupProxyFeature (/Users/sergey/work/my/js/webpack-dev-server-proxy-issue/node_modules/webpack-dev-server/lib/Server.js:169:62)
at Object.proxy (/Users/sergey/work/my/js/webpack-dev-server-proxy-issue/node_modules/webpack-dev-server/lib/Server.js:369:16)
at /Users/sergey/work/my/js/webpack-dev-server-proxy-issue/node_modules/webpack-dev-server/lib/Server.js:449:24
at Array.forEach (<anonymous>)
at Server.setupFeatures (/Users/sergey/work/my/js/webpack-dev-server-proxy-issue/node_modules/webpack-dev-server/lib/Server.js:448:22)
at new Server (/Users/sergey/work/my/js/webpack-dev-server-proxy-issue/node_modules/webpack-dev-server/lib/Server.js:68:10)
at /Users/sergey/work/my/js/webpack-dev-server-proxy-issue/node_modules/@webpack-cli/serve/lib/startDevServer.js:34:24
at Array.forEach (<anonymous>)
[email protected]:sprilukin/webpack-dev-server-beta4-proxy-issue.gitnpm install && npm run startHere is the piece of code where exception is actually thrown:
proxyOptions.logLevel = getLogLevelForProxy(
this.compiler.options.infrastructureLogging.level
);
Here this.compiler.options is an Array, not an Object in case of multiple webpack config env.
Yep, bug
I still get the same issue, has this fix been tagged?
Most helpful comment
I still get the same issue, has this fix been tagged?