Answer the question
In order to leave comments, you need to log in
Does it mean that with the transition to HTTP / 3 (HTTP / 2) it will not be necessary to pack all js files into one bundle?
HTTP of the next generations can aggregate requests, reduce the number and ping in requests, and a lot of magic. Does this mean that by supporting only HTTP/2 and/or HTTP/3, it will be possible, roughly speaking, to abandon webpack and switch to ES modules?
Answer the question
In order to leave comments, you need to log in
And someone canceled the prefetch?
The lower layer protocol is unaware of the higher layer behavior. And the server gives exactly what is requested, and there is no magic. The file came, parsed, the browser said they say I need something else, the request is gone.
Bundles will probably become a little less relevant (because yes - in one request, the client (browser) will be able to request a bunch of images at once, for example, or a bunch of separate js files). But webpack will not go away very soon - it not only packs the code into bundles - it also fixes the code (all sorts of babels work there), optimizes css (launches all sorts of preprocessors - less, scss), prepares svg (icons) and other processes produces.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question