Fix the plugin state for async modules in webpack plugins (#62998)
### What Use the plugin state directly in flight plugins to access the async modules collection ### Why This change is cherry-picked from #62349 , where I found the plugin state didn't store the async modules reousces properly due to the clone of the array in flight manifest plugin. So for flight manifestp plugin itself, it's holding a different instance rather than the one from proxy state. Closes NEXT-2743
Showing
Please
register
or
sign in
to comment