Electron Releases

Description of Change

Two Node patches existed only to hand Electron things it can reach on its own:

• refactor_allow_embedder_overriding_of_internal_fs_calls stashed internalBinding on process during bootstrap so lib/node/asar-fs-wrapper.ts could grab (and delete) it. The wrapper runs as a builtin with Node's internal require, and require('internal/bootstrap/realm') already returns the loader exports including internalBinding, so it takes it from there and process.internalBinding never exists.
• expose_get_builtin_module_function exported node::binding::get_linked_module() so sandboxed preloads (no node::Environment) could find a linked binding by name in shell/renderer/preload_utils.cc. Electron's own NODE_LINKED_BINDING_CONTEXT_AWARE macro now also emits a get_linked_module_<name>() accessor next to each binding, and NodeBindings::GetLinkedBinding() resolves a name against the same per-process binding lists RegisterBuiltinBindings() uses; preload_utils.cc calls that instead. This also retires the TODO(codebytere) in the patch.

Verified on Linux: asar reads/stat in the browser, renderer and ELECTRON_RUN_AS_NODE, process.internalBinding absent everywhere, a sandboxed preload using ipcRenderer, and the asar, ipcRenderer and process spec files pass.

Checklist

• I have built and tested this change
• I have filled out the PR description
• I have reviewed and verified the changes
• npm test passes

Release Notes

Notes: none