GoogleChromeLabs/squoosh

Release codecs on NPM

Open

#280 opened on 2018年11月13日

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

説明

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

コントリビューターガイド

技術スタック
typescriptnodejscpp
領域
releasedeveloper experience
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
over 1 week
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
needs maintainer response
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
mostly clear
前提条件
npm publishing experiencenative module compilationcross platform CI
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
25
調査方針
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.