Feature request: diagnostics output that lists what resources are in each bundled resource


Can you please add a comma delimited list of the resources contained in each bundle?

Either as commented out html right next to the <script> or <link> tag for the bundled resource, or commented out within the bundled resource itself.
Closed Nov 14, 2012 at 5:50 PM by Piedone
Fixed in changeset 7f245c2a74b3


Piedone wrote Nov 14, 2012 at 12:02 PM

What would be the specific use-case?
BTW if you disable minification you can recognize the resources building up a bundled file, in that case if you write comments those are preserved as well (however I'm not sure this latter one will work with the image-sprites branch, as ExCSS is stripping out comments AFAI remember).

TheMonarch wrote Nov 14, 2012 at 3:47 PM

The use case is something that happens often; there are many different scenarios in which one would want to identify which resources are in each bundle.
  • I push a new build to my site in production or staging, and I want to look into an issue
  • I am working on an issue in development and want to compare to production
  • I have deployed a new build and want to make sure bundles contain changes in original resources (sometimes I have to trigger cache refresh; or sometimes issues with some machines in farm serving outdated bundles)
  • When I was debugging the issue a few weeks ago about resource url's within .css when running under Azure, I repeatedly had to identify which bundle to look into in order to troubleshoot the Azure blob URL problem
  • Right now I'm looking into a potential issue where the same page loaded with two different content id's ends up loading a completely different set of bundled resources (bundles have different names, and slightly different file sizes).
  • When trying to use the "resource sets" feature I also came across this difficulty. Trying to see if I had the resource sets set up the way I wanted was very hard and I eventually gave up because it took too much time to verify what was happening.
Disabling minification is overall not much easier than looking through the minified bundles because it requires changing the settings through the admin (and if you are in a farm you run into issues of having to refresh the bundles on all the machines, given the new settings). It also takes extra time to wait for the settings to save, empty the cache, and change the settings back, and if you are bundling resources that you didn't write, you can't rely on the comments to identify the resources.

Piedone wrote Nov 14, 2012 at 5:25 PM

Sound reasonable, thanks for the clarification. Will look into this.

Piedone wrote Nov 14, 2012 at 5:49 PM

Fixed in changeset 7f245c2a74b3

Piedone wrote Nov 22, 2012 at 7:31 PM

Would you mind trying it out?