Enable Node.js Integration in NW.js Renderer Windows and Package for Distribution
Enable Node.js in NW.js renderer windows, verify require() in DevTools, and package with nw-builder.
Loading…
ReadMeFeed / Community knowledge
#nwjs
Real questions. Useful conversations. Find the people who know your stack.
nodewebkit
nodejsPackaging NW.js desktop apps across Windows, macOS, and Linux
Use nwbuild to create platform installers from one project, then verify Node integration settings before shipping.
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.
Safe 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.
Packaging an NW.js Desktop App: Manifest, Node-in-Renderer Access, and Distribution
Build a folder-based NW.js package from scratch: configure package.json, enable Node require() in the renderer, verify the runtime in DevTools, and distribute an app.nw archive without breaking native module ABI compatibility.
NW.js Single-Context Architecture: Why Direct Node Access in the Renderer Changes Desktop App Design
NW.js merges Node.js and Chromium into one JavaScript context—letting you call require('fs') directly from HTML. That convenience reshapes threading, security, and distribution. A worked example shows the pattern and the pitfalls.
Diagnosing NW.js Startup Failures on Windows: Missing DLLs, ABI Mismatches, and Cache Corruption
An NW.js app that crashes or shows a blank window on Windows usually has a missing VC++ runtime, an ABI-mismatched native module, or a corrupt cache. Here's how to tell which and fix it.
NW.js's Two JavaScript Contexts: The Architecture Decision That Makes or Breaks Your Desktop App
NW.js runs two JavaScript contexts — Node and window — and the node-remote manifest field decides which pages get full OS access. Here's how to scope it tightly and bridge the two safely.
NW.js Mixed Context vs. Separate Context: Picking the Right Boundary for Node and the DOM
NW.js can run Node.js and the DOM in one JavaScript context or two. Here's what mixed vs. separate context actually changes for security, native addons, and migration — plus how to verify which mode your app runs in.