Why aren’t built‑in ESM exports synced automatically?

[ExE-Boss]

Currently, it’s necessary to manually call Module.syncBuiltinESMExports() after making changes to built‑in exports.

This makes me wonder why wasn’t this implemented using a Proxy‑based sync‑on‑write mechanism.

A Proxy‑based sync‑on‑write solution could also only update the exports that changed, instead of looping over all built‑in modules and their exports.

[bmeck]

This was the case (we did use a Proxy), but problem with accessors (particularly getters) caused issues. See:

• esm: globals should be wrapped to stay in sync with ESM node#29426
• https://github.com/nodejs/modules/blob/master/doc/meetings/2019-09-25.md#nodejsnode
• esm: remove proxy for builtin exports node#29737

[MylesBorins]

I'm going to go ahead and close this as it seems like the original question was answered