[Feature]: add 103 Early Hints / automatic `Link` headers support
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 5.9k
- Forks
- 426
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 11
Description
Duplicates
- I have searched the existing issues
Latest version
- I have tested the latest version
Summary 💡
HTTP 103 Early Hints and the Link header provide ways to hint clients to start downloading resources before getting the main response. This can be used for improving FCP by hinting clients to start downloading route-level assets.
h3 also provides support for writing early hints on Node, so that could also be utilized.
While using early hints would be the most performant approach, support for the feature is currently limited to Node. Therefore, leveraging both would provide a safe fallback.
Examples 🌈
This feature has been (partially) implemented in Nuxt and SvelteKit.
Motivation 🔦
Better FCP!
Contributor 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.
Research direction
No repository files or tests are named. Start with the linked HTTP 103 and Link header references, then review h3's writeEarlyHints example and the Nuxt and SvelteKit implementations; done means supporting early hints where available with a safe Link-header fallback.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, typescript
- Domain
- backend, performance
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100