Enable nodeIntegration or Use Preload Scripts: Which Safeguards the Renderer Process in NW.js?

Goal

The aim is to protect the renderer from malicious or accidental access to the full Node.js runtime while still allowing developers to use native modules when needed.

Constraints & Uncertainty

• NW.js ≥0.54 disables nodeIntegration by default for security.
• When nodeIntegration is disabled, developers can expose a limited API surface via a preload script and contextBridge.
• Documentation does not clearly state whether contextIsolation is automatically enforced when nodeIntegration is off; some builds still allow direct access to Node globals due to legacy flags.
• There is no defined migration path for projects that rely on global Node APIs to the safer preload pattern.

Unresolved Decision

Which approach—enabling nodeIntegration for convenience or using a preload script for isolation—offers the best balance between security and developer ergonomics, and how does NW.js currently enforce contextIsolation when nodeIntegration is disabled?

Specific Questions

1. Does NW.js enforce contextIsolation when nodeIntegration is disabled, or can legacy flags still expose Node globals?
2. What migration steps are recommended for existing projects that rely on global Node APIs to move to a preload‑based API surface?