GoogleChromeLabs/squoosh

Don’t download all codecs

Open

#1040 opened on Jun 2, 2021

View on GitHub
 (2 comments) (3 reactions) (0 assignees)TypeScript (20,335 stars) (1,431 forks)batch import
UIhelp wanted

Description

We already delay downloading til the user actually loads an image, but with codecs getting bigger, we might want to allow the user to download individual codecs.

There’s a bit of UI work to be done here (can we add download buttons to the codec drop down?) and we prob. need to think about how to handle missing codecs when offline to generate meaningful error messages here.

Contributor guide

Tech stack
typescripthtmlcss
Domain
frontend
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Basic TypeScript knowledgeUnderstanding of UI event handling
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
45
Research direction
Check the current codec download flow in the Squoosh codebase (likely in src/lib/codecs or similar). The issue suggests adding download buttons to the codec dropdown component. Investigate how codecs are currently loaded and where the dropdown is rendered. Consider how to handle offline scenarios when a codec is missing; possibly show a meaningful error message. Look into existing patterns for async loading and state management. Review the UI component for codec selection to understand the current structure.