webpack / webpack/webpack-dev-server
listening as both https and http server simultaneously
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 7.8k
- Forks
- 1.5k
- Avg merge
- 5h 32m
- Merged PRs (30d)
- 6
Description
Hi,
I'm moving a project over from browserify to webpack and hit a snag this afternoon. For arcane reasons (involving chrome and atom-shell/chromium behaviors) I need both https and http instances of local dev/testing web servers.
webpack-dev-server is awesome, but I didn't find any directly supported way to instantiate on two ports at the same time.
Here's what I ended up doing (full code context, farther down below)...
webpack_dev_server.listen(8004);
http.createServer(webpack_dev_server.app).listen (8005);
I'd like to ask whether this is a reasonable solution, or whether there's a better thing I should be doing, or alternatively whether a pull request to implement simultaneous https/http at the API level would be welcome.
Below, the full gulpfile.js chunk ...
var webpack = require ("webpack");
var WebpackDevServer = require ("webpack-dev-server");
var webpackConfig = require ("./webpack.config.js");
var http = require ('http');
gulp.task ("webpack-dev-server", function (callback) {
// modify some webpack config options
var myConfig = Object.create (webpackConfig);
myConfig.devtool = "#source-map";
myConfig.debug = true;
// Start a webpack-dev-server
var wds = new WebpackDevServer (webpack(myConfig), {
https: true,
publicPath: "/web", // + myConfig.output.publicPath,
stats: {
colors: true
}
});
wds.listen(8004);
http.createServer(wds.app).listen (8005);
});
Thank you.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the supplied gulpfile.js example and the WebpackDevServer constructor and listen calls. Review the server API and related tests for multiple listeners, then determine whether simultaneous HTTP and HTTPS requires a supported API or documentation change. Done means the intended behavior is explicitly defined and both ports can be verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, webpack
- Domain
- devtools, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100