Difficulty extracting historical build metrics from rsdoctor output

[grvdisco]

Hi team,

I’m trying to use rsdoctor to keep track of historical build metrics over time, including details like build time, bundle sizes, and duplicate packages. My goal is to store this information in a .csv file so I can plot trends and gain insights into how these parameters evolve across builds.

I’ve tried enabling the following config parameter:

brief: { writeDataJson: true }

This resulted in a single manifest.json file that references a base64-compressed JSON file. After decompressing it, I still couldn’t derive meaningful metrics or data in a straightforward way that matches what the dashboard shows.

While exploring the rsdoctor codebase, I noticed that under the hood modern.js is used, along with an SDK that seems to be responsible for decompressing and translating the data into human-readable metrics. Unfortunately, I’m not familiar with modern.js, which makes it challenging to fully understand and extract these metrics.

Request:
Could you provide any guidance, documentation, or code references that explain how to properly decompress and interpret the rsdoctor data so I can map it to build metrics and store it externally (e.g., in a .csv file)? If there’s a known workflow or tool for this, I’d appreciate learning about it. And if there’s no existing solution, I’d be happy to try creating a PR—just point me in the right direction!

Thanks in advance for your help.

[easy1090]

Ok, I'll think about this and write a document for this situation this month.

[grvdisco]

Thanks! @easy1090 🖖