Diagnosing Blank Windows and Missing Node APIs in NW.js
A diagnostic guide for NW.js apps that launch blank or fail with require is not defined, covering manifest checks, renderer probes, and native module fixes.
Loading…
ReadMeFeed / Community knowledge
#node-integration
Real questions. Useful conversations. Find the people who know your stack.
nodewebkitSafe Node Access in NW.js: Preload Scripts Over Full Renderer Integration
Enable Node integration in NW.js without exposing the full runtime to your renderer by combining context isolation with a preload-based API surface.
Resolving 'require is not defined' and Node API Failures in NW.js
A diagnostic guide for fixing 'require is not defined' and Node API access failures in NW.js renderer processes, including manifest configuration and CSP fixes.
Nodewebkit nodeIntegration: How to Enable, Use Safely, and Avoid Pitfalls
Enable nodeIntegration in Nodewebkit safely: configure BrowserWindow, use preload scripts, avoid synchronous calls, and test boundaries. Follow best practices to keep your desktop app secure.
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 Un
ContextIsolation: Limits on Legacy Node Integration in Electron v15+
Goal Developers migrating an Electron application to v15 or later face a choice: keep contextIsolation disabled to preserve legacy code that relies on nodeIntegration , or enable it for the security benefits it offers. The core question is how this decision affects existing renderer scripts that directly access Node.js APIs. Uncertainty Electron’s documentat
electronEnable 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 scrip
Node Integration versus Remote Module/ContextBridge for Secure NW.js Production Builds
Goal: Select a method for exposing necessary Node.js functionality to the renderer process in an NW.js application that remains secure when the app loads remote content in production. Constraints: The chosen approach must prevent code‑injection attacks, require an explicit whitelist of modules, and ensure that any preload script used to bridge Node APIs reso
Direct Node.js require() versus IPC‑mediated file access in nodewebkit: balancing convenience against security constraints
nodewebkit applications must decide how to grant renderer processes file system access while respecting security boundaries. Enabling nodeIntegration: true allows direct require() calls from the renderer, eliminating IPC overhead but exposing the host environment to potentially malicious web content. Disabling nodeIntegration and routing file requests throug