Is there a way to leverage running the webpack-dev-server on https when configuring using CLI?
The problem is the connection to
socket.io
is overhttp
and nothttps
.
A workaround exists, but its very annoying.
webpack-dev-server
in your index.html
<script src="https://localhost:8080/webpack-dev-server.js"></script>
webpack/hot/only-dev-server
.app: [
'webpack/hot/only-dev-server',
'./app.js'
],
// ... more entry points that include the same [] ...
Yes there is a way to configure webpack-dev-server on https when configuring using CLI.
The solution is to not use --inline
option.
There are many ways to configure the server and --hot
. The one to follow, assuming your not creating a custom server implementation/middleware (Might be the same), is detailed in the docs.
http://webpack.github.io/docs/webpack-dev-server.html#webpack-dev-server-cli
<script src="https://localhost:8080/webpack-dev-server.js"></script>
webpack/hot/only-dev-server
into the entry.{
"scripts": {
"start": "webpack-dev-server -d --hot --https --config webpack.config.development.js"
}
}
var webpackConfig = require('webpack-config');
module.exports = webpackConfig.fromCwd().merge({
devServer: {
colors: true,
contentBase: './build',
historyApiFallback: true,
inline: true,
progress: true
},
devtool: 'eval-source-map'
});
Main webpack configuration is not listed here.
I think you might add this line to the entry point to also create a secure socket connection:
"dev-server": "webpack-dev-server/client?https://localhost:8080/",
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With