Open zackarychapple opened 3 days ago
@zackarychapple This is planned, but because the Rsdoctor data is too large, the integration into an html may be slow and the page interaction may even crash. Therefore, the report after streamlining the data may be displayed. For example, the following key data:
Error in the rules;
Each Loader compiles time-consuming; (But, no display of the code before and after compilation for each file by each Loader);
Each plugin takes time;
Tree circle of products Bundles and Modules (no code details display).
Is the above plan in line with your idea?
The biggest issue is that folks are wanting to add the Rsdoctor reports as something that is an artifact generated by the build pipeline for historical and reporting reasons. Without an "offiline" way to output everything its challenging. @easy1090 we can chat through in more detail in DM's if you want.
The biggest issue is that folks are wanting to add the Rsdoctor reports as something that is an artifact generated by the build pipeline for historical and reporting reasons. Without an "offiline" way to output everything its challenging.
I can understand this problem.
@zackarychapple Yes, I'm glad to talk more about this in DM's. lark or discord?
What problem does this feature solve?
Right now the only way to see the report is to have the page launch with rsdoctor cli or the plugin itself.
What does the proposed API look like?
have a configuration that supports
reportFilename
similar to bundle analyzer. This would allow for folders to be created with the config name and other options such as below. This helps with uploading to CI/CD reporting servers for later viewing without needing to download the manifest and run the cli.reportFilename: `${BUNDLE_ANALYZER}/report-${ CONFIG.name }-${Date.now()}.html`,