GoogleChrome/lighthouse

Update minify-trace to exclude unnecessary trace data

Open

#12,748 建立於 2021年7月5日

在 GitHub 查看
 (2 留言) (0 反應) (0 負責人)JavaScript (27,768 star) (9,278 fork)batch import
P3good first issue

描述

PR https://github.com/GoogleChrome/lighthouse/pull/12692 included additional trace categories.

With these changes, a run on the verge gives a trace of: before: 50.1MiB after: 60.7MiB

We should teach minify-trace to exclude the unnecessary entries.

貢獻者指南

技術棧
javascriptnodejs
領域
performanceobservability
議題類型
performance
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
3
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
half day
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
fresh
清晰度議題是否清楚說明預期改動、驗收標準和下一步。
mostly clear
前置要求
Understand minify trace moduleFamiliarity with trace categories
新手友善度1-100 的估計分數，表示該議題對首次貢獻者的友善程度。
50
研究方向
Examine the 'minify trace.js' file to understand current filtering logic. Identify which trace categories are unnecessary (e.g., from PR #12692) and implement a method to exclude them, possibly by adding a configurable list or filtering based on category names. Test the change by comparing trace sizes before and after.