ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #nodewebkit
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.
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.
Enabling nodeIntegration in NW.js gives renderers direct Node.js access, but it also removes the sandbox. Here's how to decide and how to replace it with a preload script.
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.
Learn how to choose between the standard Window object and the NW.js Window API to manage native OS behaviors like frameless windows and always-on-top states.
nodejs
javascript