HTTP/2 dev server

Open
#1,027 4 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

  • #206 by @ProgramRipper — closed without merging

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
nuxt, typescript
Domain
cli, networking

Research direction

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.

Written by the indexing model from the issue text.

Description

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
Dominant language
TypeScript
Stars
402
Forks
125
Avg merge
2d 9h
Merged PRs (30d)
37

Getting set up

Open in Codespaces

Starts the project's dev container in your browser, under your own GitHub account.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nuxt/cli

All issues in nuxt/cli

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.