HTTP/2 dev server
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
- Read the contribution guide.
- Check existing discussions and issues.
- Dominant language
- TypeScript
- Stars
- 402
- Forks
- 125
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 37
Getting set up
Starts the project's dev container in your browser, under your own GitHub account.
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from nuxt/cli
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
dev: false "reachable from the network" warning when `devServer.host` is a `*.localhost` subdomainMay be free again A pull request for this issue was closed without being merged. Open
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 55/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
ai-driven-qa bug claude Cosmetic
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
Domain / chatbot New
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Inist-CNRS/lodex#3861 ·
Maintainers usually reply within 1 day
-
area:agent-sdk area:docs documentation enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
anthropics/claude-code#110914 ·
-
area/cli platform/windows type/bug version/v2
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
anomalyco/opencode#64631 · 1 comment ·
Maintainers usually reply within 1 day