nodeIntegration Default Configuration Limits

Node.js Integration Defaults

NW.js allows the integration of Node.js globals directly into web pages, enabling the use of require and process within the Chromium renderer. While this functionality is central to the platform's architecture, the official documentation does not explicitly define the default state of the nodeIntegration setting.

Configuration Uncertainty

Current releases appear to expose Node globals by default without requiring explicit configuration in the manifest. However, the lack of a documented default value creates uncertainty regarding the long-term stability of this behavior. Developers relying on implicit Node availability may face breaking changes if future releases transition to a "secure by default" model where integration must be opted into.

What is the officially intended default value for nodeIntegration in recent releases? Is there a documented roadmap to change this default for security reasons?