fix: sort ConcatenatedModule export keys for deterministic builds

[mango766]

Summary

Sort exports_map entries by key before rendering the __webpack_require__.d(exports, {...}) object in ConcatenatedModule.

exports_map is a HashMap<Atom, String>, so .iter() produces non-deterministic iteration order. This means the same source code can produce different export key ordering across builds, leading to different content hashes for the same chunk — even with no code changes.

The fix collects entries into a vec, sorts by key, then builds the definitions string. This matches the approach already used in ESMExportInitFragment (init_fragment.rs:356) where export_map is sorted before rendering.

Related links

Closes #13182

Checklist

• Tests updated (or not required).
• Documentation updated (or not required).

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6594e19f01

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

[codspeed-hq]

Merging this PR will not alter performance

✅ 23 untouched benchmarks
⏩ 3 skipped benchmarks¹

---

_{Comparing mango766:fix/deterministic-concatenated-module-exports (6594e19) with main (a4e0229)}

Footnotes

1. 3 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩

[JSerFeng]

Thanks

You can use IndexMap directly to avoid sorting, and you could do the same for unused and inlined exports as well if you don't mind