I love disc and it's helped our browserify build quite a bit. But I would love to have a reporter option that does just a high level overview straight to STDOUT in a console friendly/ascii format.
The key metrics that most people (I think) care about when looking at their browserify bundle is:
size of the browserify-core in bytes and %
size of node_modules in bytes and %
size of actual library in bytes and %
These three (six with percentages) are all that I care about at a quick glance to ensure that my module is trending the direction that I want.
To go just a step further, I would like to see just a single-level below each of the items above, to see how browserify-core weight, how node_modules weight, and how actual library weight is distributed.
This would be small enough output that emitting to the console would be easily digestable and useful as a quick report. If something trends in an undesirable direction, then one can switch over to the full HTML reporter and dive in deeper.
levity
commented
8 years ago
I love
discand it's helped our browserify build quite a bit. But I would love to have a reporter option that does just a high level overview straight to STDOUT in a console friendly/ascii format.The key metrics that most people (I think) care about when looking at their browserify bundle is:
These three (six with percentages) are all that I care about at a quick glance to ensure that my module is trending the direction that I want.
To go just a step further, I would like to see just a single-level below each of the items above, to see how browserify-core weight, how node_modules weight, and how actual library weight is distributed.
This would be small enough output that emitting to the console would be easily digestable and useful as a quick report. If something trends in an undesirable direction, then one can switch over to the full HTML reporter and dive in deeper.