GoogleChromeLabs/squoosh

Release codecs on NPM

Open

#280 opened on Nov 13, 2018

View on GitHub
 (10 comments) (55 reactions) (1 assignee)TypeScript (20,335 stars) (1,431 forks)batch import
codecgood first issuehelp wanted

Description

Hi,

do you consider releasing the codecs ( optiping / mozjpeg ...) as npm packages ? I've tried to build them myself in the past but failed to do so.

I use imagemin in my toolbelt to compress images at build time, but as it relies on binaries downloaded on install, it's very painful on a corporate environment without internet access on build machines.

I'm pretty sure more people than just me would be interested in such a feature : https://github.com/imagemin/optipng-bin/issues/71

Contributor guide

Tech stack
typescriptnodejscpp
Domain
releasedeveloper experience
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.
over 1 week
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
needs maintainer response
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
npm publishing experiencenative module compilationcross platform CI
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Investigate the existing discussion in the issue comments. Look at how imagemin's optipng bin and mozjpeg bin packages are structured. Consider setting up CI to build the codecs (like optipng, mozjpeg) for multiple platforms and publish them as npm packages. Reach out to the repository maintainers to confirm interest and get guidance on the preferred architecture (e.g., using prebuild or node pre gyp). Also check if there is an existing assignee or ongoing work.