webpack-dev-server
webpack-dev-server copied to clipboard
webpack
Question: What is the status of HTTP/2 support?
- Operating System: macOS 10.14.3
- Node Version: 10
- Yarn Version: 1.13.0
- webpack Version: 4.29.4
- webpack-dev-server Version: 3.2.1
- [ ] This is a bug
- [ ] This is a modification request
- [x] This is a question
I spent about an hour digging around yesterday and couldn't find the answer to this question, so I wanted to post here and get some insight.
I read through https://github.com/webpack/webpack-dev-server/issues/516, which seems to indicate there is HTTP/2 supported, but I couldn't find any docs on how to enable it. All I found in the official docs was the line under this section https://webpack.js.org/configuration/dev-server/#devserverhttps saying that it can run with HTTP/2.
In the code in this repo I found this https://github.com/webpack/webpack-dev-server/blob/21687c3bfc95752957d16470b97d281001dc6a07/lib/Server.js#L633-L660
All of which links to issues and other repos which have either been closed or have no work being done on them. And according to this comment https://github.com/webpack/webpack-dev-server/issues/1493#issuecomment-419493497, it is planned for v4, but nothing in the 4.0.0 milestone https://github.com/webpack/webpack-dev-server/milestone/4 seems to support that statement.
Ultimately, I'm confused as to the current situation. Does Webpack-Dev-Server support HTTP/2? If not, will it be supported in the future?
We support http2 using spdy module for backward compatibility with old node version, to enable http2 you should enable https option and spdy option, but i agree it is misleading, and looks we doesn't respect spdy (https://github.com/webpack/webpack-dev-server/blob/master/bin/options.js), thanks for issue. We need:
- Respect
spdy(add aliashttp2) in CLI - Add tests
For future version use http2 module instead node-spdy
As an added note, will respecting the spdy option in the CLI also reflect if I am using this programmatically by importing webpack-dev-server?
@evilebottnawi I'm a bit confused: the options file you linked contains no mention of spdy or http2 (or http/2). I've played around with this all evening, and I cannot get webpack-dev-server to serve over http2. Setting a CLI option does nothing, and the same is true for devServer.https.spdy: true (devServer.spdy causes a validation error).
I see it looks like it's coming in #1721, but it sounds like it was there before?
@jshado1 yep, now it is broken, this PR solve problem, next week release
Fixed https://github.com/webpack/webpack-dev-server/issues/1713, http2 doesn't support on node >= 10 due express doesn't support this right now, we fix it after express was released
@hullevive we use express under webpack-dev-server, so if you want http2 support please write this in express issue, we can't do something on our side
Still an issue in 2020? Trying to setup a localhost with https.
I'm getting : HTTP/2 is currently unsupported for Node 10.0.0 and above, but will be supported once Express supports it
Is there a release that has some sort of workaround? Even if it's dirty, I just need HTTPS for my vue app that uses webpack, thanks!
@ereztdev please write about it in express repo, they still not implement http2 support in 2020
@evilebottnawi Is there a workaround in the meantime with node > 10.0 ? Using http/1.1 is so slow for development...
Edit: Here is example of a caddyfile to run a caddy reverse proxy for http/2:
localhost:3001
reverse_proxy 127.0.0.1:3000
tls localhost.pem localhost-key.pem
devServer should be run on port 3000 in this case. And caddy reverse proxy listens on port 3001. If you need to generate local certificates, I recommend mkcert
@Herz3h you can launch nginx or caddy and setup proxy to webpack-dev-server
spdyis effectively unmaintained
It just got an update this year after a long break, perhaps we should reconsider using it when developers explicitly want to? I'm using spdy for my personal project (it serves HTTP/2 well - unlike http2) and so far have no major issues with it on newest Node (14.x).
The issues preventing spdy from working on node > 11.1 are now fixed, btw: https://github.com/spdy-http2/handle-thing/pull/13
Node 15.0.1 have HTTP/3 QUIC experimental support. webpack-dev-server will implement that ?
How feasible would it be to use a different framework than Express to power webpack-dev-server? Express 5.0, which is tilted to have full http2 support, has been in alpha for about 7 years now, and there is no clear roadmap indicating when it will be released. Competing frameworks (koa, fastify etc) have all supported it for years and are actively maintained.
I asked the developers about the maintenance status and roadmap, and it seems to mostly boil down to them not having the resources and hoping the community will pitch in: https://github.com/expressjs/express/issues/4451
we are looking at fastify for the our next default development framework
Express have thrown in the towel on http2: They've essentially said they're married to an underlying dead lib, spdy, for http2 support, so Express is unfortunately dying a slow death.
Guys, this is awkward, but... I just checked and http2 flag.... Works? Looks like the specific check that prevented it from being enabled on Node 10+ is gone from lib/Server.js with this change:
https://github.com/webpack/webpack-dev-server/commit/b0161e9852cdf41730e82aa43efe7e88f44a4f9d#diff-b706bbadb3d2315d99678f05e1f4bfd78a4bb4a7a6c65f3e81f1386fee3c883aL669-L678
So webpack-dev-server 4.0.0-beta.0 and up should run http/2 just fine. And it does!
Can confirm that https: true works great in 4.0. Awesome work @alexander-akait
...however, http2 is quite unstable. Pretty sure that has to do with the SPDY package though.
Yep, if we need http2, we need fix compatibility with http2 module in express or migrate on fastify or other frameworks, it requires more work, firstly we should do compatibility inside webpack-dev-middleware, but there are more middleware which require compatibility too
Seems like http2 is being supported now, but I observed that the proxy downgrades requests from http2 to http1.1, which was weird 🤔 Is that a known issue?
