HTTP/2 can't. But it can't make builds less complex. You're not longer bundling every script, inlining every image, etc.
I don't see how you can work on a modern JS application, understand HTTP/2, and think HTTP/2 replaces Webpack. Pick two...
Webpack is used for a lot of things -- that it should not be used for. As I posted above many of the things it is used for should out of band of your blunder.
HTTP2 removes the need for bundling by allowing a smart web server either learn, or be told what files will be required for rendering to be pushed on the first request from the client. This eliminates the multiple request / and connections required in HTTP1 -- even with 4 pipelines that can be a lot of round trip request. If your application was not smart enough to know what to push to the client HTTP2 can allow multiple request over the same connection again negating the need for bundling.
> it is incorrect to say that HTTP/2 is a replacement for Webpack.
Take a look back over the thread. They didn't say that. They said it was a step in the right direction. Then somebody started putting words in their mouth.
We did a lot of study and testing on HTTP/2 and we found that your claims are entirely incorrect. But don't take my word for it, see the stats!
https://medium.com/webpack/webpack-http-2-7083ec3f3ce6
HOWEVER! HTTP/2 and webpack become even more powerful when used together! This is something we are really excited to share and build on!