babel/minify

Add benchmarks that show transpilation + minification times

Open

#95 opened on 2016年8月26日

GitHub で見る
 (2 comments) (8 reactions) (0 assignees)JavaScript (4,377 stars) (223 forks)batch import
help wanted

説明

What people actually care about w.r.t. build times is usually the end-to-end time. Talking with @skevy, we were saying a typical production build pipeline will transpile and minify, which previously entailed running Babel (ex: with es2015 preset) and then Uglify. But now a pipeline could run just Babel (ex: with es2015 + babili).

The perf benchmarks currently make Uglify look way better than Babili to people who prefer 1.5-2x faster build times for roughly the same end result, but if the actual end-to-end build times that comprise transpilation and minification are faster, that'd change a lot of minds.

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

技術スタック
javascript
領域
performance
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-2 days
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
mostly clear
前提条件
Node.jsnpmBabel basics
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
50
調査方針
The issue requests adding benchmarks to compare end to end transpilation and minification times. A contributor should first explore the repository for any existing benchmark infrastructure (e.g., a 'benchmark' folder or scripts in package.json). Then design a test that runs Babel with the es2015 preset and minifies using both Babili and Uglify, measuring the total time. Findings should be documented and results presented. Key files to look at include package.json and any existing benchmark scripts.