ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Developer tools · #nodewebkit
Goal: Enable NW.js mixed context mode so that UI scripts can directly call Node.js modules such as fs while the application enforces a Content Security Policy that restricts script sources to same‑origin. Constraint: In mixed context the Node.js globals are exposed on the window object, which may bypass the browser’s CSP script‑src checks; it is unclear whet
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
Cache Invalidation in NW.js NW.js applications utilize an embedded Chromium content shell, meaning resources loaded via DOM or network paths are subject to standard HTTP caching. This behavior creates a discrepancy where assets loaded via Node.js require() bypass the cache, while web-standard assets persist in the user-data directory across application resta
Integration of Node.js and Chromium Renderer In NW.js applications, developers can utilize the node-main script to initialize application state in a background Node.js context before any browser windows are instantiated. This architecture allows for system-level operations to run independently of the Chromium rendering process. A design challenge arises when
Node.js Integration in Mixed Contexts NW.js allows the execution of Node.js APIs directly within the DOM context by setting "nodejs": true in the package.json configuration. This integration enables seamless access to the filesystem and OS-level operations from the client-side JavaScript environment. Security Boundary Constraints A critical design concern ar
I am building a desktop app on NW.js (assume a recent 0.8x release; I will confirm the bundled Chromium version via nw.process.versions ) that surfaces background events from the Node context — file watcher hits and scheduled sync results — as desktop notifications using the standard HTML5 Notification constructor in the window context. The design concern is
A packaged NW.js application relies on the bundled Chromium accessibility tree to expose DOM roles, labels and states to native assistive technologies. The user-facing workflow needs predictable screen reader compatibility across platforms, but there is no documented NW.js configuration that explicitly controls or tests that mapping. Accessibility support is
nodewebkit utilizes a child-process architecture to isolate the WebKit engine from the Node.js parent process. While this prevents a renderer crash from terminating the entire application, the library relies on shared memory buffers for data transfer between the environments. When performing rapid-cycle restarts or interrupted upgrades, there is an indicatio
Failed global shortcut registration in nw.App.registerGlobalHotKey When an NW.js application calls nw.App.registerGlobalHotKey , the API returns a boolean. A return value of false indicates that the registration did not succeed, but the documentation does not expose the underlying reason—whether the shortcut is already in use by another process, the accelera
nodejs