Packaging 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.
ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Use nwbuild to create platform installers from one project, then verify Node integration settings before shipping.
Learn how Tauri’s Rust‑backed File System API lets you safely read and write files from JavaScript, keeping your desktop app lightweight and secure. Follow a concrete example, trade‑offs, and practical next steps.
Learn how to implement and secure the Tauri auto-updater to push over-the-air updates to your Rust-backed desktop applications using manifests and code signing.
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.
Setting decorations: false in Tauri is one line of config — but you inherit dragging, resizing, snap behavior, and per-platform quirks. Here's a working setup and what to verify.
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.
Discover how Tauri’s fs module lets you read, write, and manage files safely in desktop apps. Learn the key design choices, a hands‑on example, and the trade‑offs you need to know.
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 Tauri's IPC system securely bridges web frontends with Rust backends using commands, with practical examples for building safe, performant desktop applications.