HTTP/2 dev server

Describe the feature

In development mode, large chunks of JS code create a large number of parallel HTTP/1.1 requests.
And browsers like Chromium limit the max-connections-per-server to 6, which will quickly become overwhelming.

In my case, a single http request would wait nearly 6 sec before being sent, with a response within milliseconds.

I tested this idea by using Caddy (which can handle HTTP/2 requests) as a reverse proxy for the development server. It successfully reduces the wait time for individual requests to milliseconds (and all in parallel!).

I believe that if the Nuxt dev server could support HTTP/2 directly, we could achieve even better performance than my workaround. 😉

Additional information

• Would you be willing to help implement this feature?
  • unjs/listhen#206
• Could this feature be implemented as a module?

Final checks

• Read the contribution guide.
• Check existing discussions and issues.

Start by reading the referenced unjs/listhen#206 discussion and the Nuxt CLI development-server entry point. Confirm how the current server handles HTTP/1.1 requests and define the validation needed for direct HTTP/2 support, including parallel asset requests and development-mode behavior.