Cache-headers and/or Service Worker
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 142
- Forks
- 230
- PR merge metrics
- No merged PRs in 30d
Description
We send Cache-control: max-age=0, so we have no caching even for the exact same asset within a single page load (e.g. playground-typescript-worker.js). We do have ETags, so it's not a full response each time, but the server still needs to read and compress the asset to check the ETag. We'll need a better caching strategy (maybe default 5 minute window, hashed asset names with longer windows, and/or service worker).
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 by inspecting repeated requests for playground-typescript-worker.js and the current Cache-Control and ETag behavior. Define and document a caching strategy for unchanged assets, then verify that repeated page-load requests avoid unnecessary asset reads and compression.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- performance, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100