fix: use RuntimeKey instead of Runtime for export generation by hai-x · Pull Request #20346

fix: use RuntimeKey instead of Runtime for export generation by hai-x · Pull Request #20346 · webpack/webpack

Summary

Fixes #20332.

What kind of change does this PR introduce?

In RuntimeSpecSet, we deduplicate runtimes by RuntimeKey, so no extra runtimes are stored here when it have same RuntimeKey.

However, when a concatenated module is generated in different chunks that share the same runtime value (equal in value but not the same reference), we still need to generate the export statement. To ensure it, we should use RuntimeKey to make sure that no runtimes are missing.

Did you add tests for your changes?

Yes

Does this PR introduce a breaking change?

If relevant, what needs to be documented once your changes are merged or what have you already documented?