ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
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.
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 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 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.
Learn how to add a system tray icon to an NW.js desktop app using the nw.Tray API, with a complete example, cross‑platform notes, and cleanup tips.
Step‑by‑step guide to create a frameless, draggable NW.js window with custom title‑bar controls, including manifest setup, HTML/CSS/JS, native‑module rebuild, verification and rollback.
Learn how to use NW.js to merge Node.js and Chromium contexts, allowing direct system access from the DOM without IPC overhead.
Learn how to securely implement nodeIntegration in NW.js by isolating trusted local content from untrusted remote data using preload scripts and CSP.
Learn how to choose between Mixed and Separate contexts in NW.js to balance native OS access with application security and stability.
nodewebkit
nodejs
javascript