[Bundle Analysis] Post-GA Work (V2?)

[aj-codecov]

Context GA Launched on September 10th to a modest bump in users, we're now at 178 (9/13) orgs total, about 2/3 of which are actively engaged and uploading reports. The goal is to push BA towards greater "actionability", but also continue to expand addressable market. In this vein there's a few things we'd like to pursue next: NOW

• Summary Bar Improvements Applications #1962
  • More context to better understand how much of your bundle is made of different aspects at a glance (recently requested via survey)
  • Designs
• 1st bundle comment Platform #1412
  • let people know they've been successful and need to push their next commit.
• Stacked area chart Visualization Applications #2568
  • Could we update the size over time chart to be a stacked area chart showing composition of bundle over time?
• New Bundle-Analyzer Onboarding support Applications #2572
  • Suejung just introduced this for people that may not use a standard bundler, we should treat it as a first class solution like the other plugins and link to it in our onboarding.

NEXT

• Finish Astro Plugin Applications https://github.com/codecov/codecov-javascript-bundler-plugins/issues/93
  • Our best option here is likely to make the OS contribution and push Nate (internal to Sentry and co-creator of Astro) to help us get it approved and merged.
• Highlight large code changes Applications + Platform #2569
  • We can link through to the diff exactly where a large change came from (asset to module to chunk to diff - here's exactly where we think this large (greater than 10%?) change happened.
• Break out by path Applications + Design #2570
  • This needs some discovery and design exploration - likely a per plugin engineering lift.
  • Example this is an astro tool that provides per path bundle sizes. Astro does path based code splitting natively and may be a good place to start, but this is likely something we can translate to other plugins as well. Tentatively we would likely go one level deep, from some quick looking, it seems two doesn't make sense.
  • Example: https://app.codecov.io/gh/codecov one level would be provider. Two levels would be org.
  • Example: https://www.notion.so/sentry/Codecov-General - this is odd, it'd be one level org (which isn't really a thing) and two levels would be an individual page.
  • Example: https://docs.google.com/document/ one level is sufficient here probably.

LATER

• [Stretch] Esbuild Plugin Applications https://github.com/codecov/codecov-javascript-bundler-plugins/issues/41
  • a ton of usage and increasing in usage faster than other bundlers, just difficult to support, but worth it IMO
• [Stretch] Rspack Plugin Applications https://github.com/codecov/codecov-javascript-bundler-plugins/issues/178
  • Sentry uses Rspack and it'd be nice to be able to have them use BA more widely
• [Stretch] Reach graph Applications #2571
  • we've talked about this historically and been hesitant to dive in. That said, we have seen feedback from the beginning that this is something users expect - if we opt not to do this for some reason, it is still likely worth our time to show visual representation of a bundle as it seems a consistent point of feedback.

Ultimately with completion of the above we will have made bundle analysis easier to use at a glance with the summary bar, and far more contextual with paths. As well as expanding usage to another bundler plugin that has the bonus of preserving the feedback channel coming from Sentry.

Plugin specific issues are all in the Bundle Analysis plugin repo

[aj-codecov]

Identify "penetration" - Number of BA orgs / Number of orgs with at least one javascript repo