Investigate selectively served polyfills
Open
Nobody has claimed this yet.
improvement
performance
- Dominant language
- TypeScript
- Stars
- 5.5k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
Polyfills bloat the main js payload, and should only be served to browsers that need them. This is done by next.js, see the writeups:
Related: #2346
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
Start with the Next.js pull request and web.dev writeup linked in the issue, then review related issue #2346. Determine how the interface currently includes polyfills and define a browser-selective approach. Done means browsers that need polyfills still receive them while the main JavaScript payload is reduced.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- next.js, typescript
- Domain
- build-system, frontend, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100