[wbinnssmith]

What?

Show source load scope in the bundle analyzer's single-build view: label async-only and mixed sources in the table, mark them in the treemap with a legend, and add an Initial only filter.

Why?

Help distinguish sources reachable only behind an async import boundary from sources reachable through an initial path (or both). This describes module-graph reachability, not when a browser actually requests a chunk.

How?

Traverse the route's active-entry module graph, propagating initial, async, and traced reachability across dependencies. Combine the reached module scopes for each source, then pass the resulting classification to the table, treemap, and filter. The new filter and indicators apply to the single-build view; the comparison view keeps its existing behavior.

Verification: Bundle-analyzer typecheck, focused lint/format checks, and production build passed; all eight combinations of the scope flags were checked when simplifying the classification logic.

[github-actions]

Tests Passed

Commit: 5c0e8b0

[wbinnssmith]

this can go with react compiler

[wbinnssmith]

Initial load only

[sokra]

Initial|Async → "mixed"

That logic doesn't make sense to me. If a module is loaded initially and async, that will cause it to be loaded initially and not async.

So I think it should be Initial|Async → Initial

[wbinnssmith]

The distinction may matter to the user: it might be surprising to turn an import async only to find it's still part of the initial payload. Showing it as mixed would be a cue that something is still retaining it synchronously.