babel/minify

Add benchmarks that show transpilation + minification times

Open

#95 建立於 2016年8月26日

在 GitHub 查看
 (2 留言) (8 反應) (0 負責人)JavaScript (4,377 star) (223 fork)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
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
1-2 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
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.