Electron nodeIntegration default and accidental public access risk

Background

Electron 12+ ships with nodeIntegration disabled by default in renderer processes. This change was introduced to reduce the attack surface when loading untrusted content. Legacy applications, however, often rely on nodeIntegration:true to access Node.js APIs directly from the renderer.

Unresolved Decision

While the documentation recommends explicitly enabling nodeIntegration only when necessary, the absence of a warning or prompt when it is enabled leaves room for accidental exposure. With contextIsolation set to true, the renderer still gains direct access to the Node.js runtime if nodeIntegration is true, bypassing the isolation boundary.

Key Constraints

• Changing the default to true may break existing code that expects nodeIntegration to be on.
• Leaving the default at false requires developers to audit their code for any implicit reliance on Node APIs in the renderer.
• No automated tooling currently flags accidental enabling of nodeIntegration.

Open Questions

1. What is the impact on application stability and security when legacy code is forced to migrate to nodeIntegration:false?
2. How can developers reliably detect accidental nodeIntegration:true in their project bundles?
3. Would a runtime warning or build‑time lint rule effectively prevent accidental public access to Node APIs?