GoogleChrome/lighthouse

Update minify-trace to exclude unnecessary trace data

Open

#12748 opened on Jul 5, 2021

View on GitHub
 (2 comments) (0 reactions) (0 assignees)JavaScript (27,768 stars) (9,278 forks)batch import
P3good first issue

Description

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.

Contributor guide

Tech stack
javascriptnodejs
Domain
performanceobservability
Issue type
performance
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.
half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
Understand minify trace moduleFamiliarity with trace categories
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50
Research direction
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.