✅ Deploy Preview for rspack canceled.

!bench

📝 Benchmark detail: Open

Can you explain the issue before ?

for example, a -> b -> c

in the first build, c has top-level-await, this will infer a and b are async modules (a (async) -> b (async) -> c (async))

but in the second build, we remove the top-level-await inside c, the correct module graph should be a -> b -> c, but since we incrementally rebuild the module graph, only rebuild the modified module c, so the module graph is a (async) -> b (async) -> c, this is an incorrect module graph

in this PR we will fix this first in InferAsyncModulesPlugin, we find the not has_top_level_await modules from affected modules, and infer is_async for them, reset is_async back to false first, and then find the has_top_level_await modules from affected modules and set them and there inferred modules to is_async: true

and when newIncremental disabled, old incremental enabled or nothing enabled at all, the affected modules is just all modules, follow the same steps, will also have a correctly updated module graph

for example, a -> b -> c

in the first build, c has top-level-await, this will infer a and b are async modules (a (async) -> b (async) -> c (async))

Why are a and b not included in affectedModules, as they have data referred from c