How 0trebor0/nodeviewjs works
NodeViewJS is a desktop runtime that hosts web apps in the operating system’s WebView and exposes a permission-checked backend command bridge rather than Node.js globals. The main workflow is a page invoking a named command, the runtime authorizing and dispatching it, and the handler returning a response; native window and WebView code host the page and bridge. The README also documents UI, helper, plugin, launch-routing, and update capabilities. Some feature wiring is documented but its implementation was not sampled, so those links cite the README.
Main entry points: app.js App lifecycle · index.js Public API · ipc.js IPC protocol · window.cpp Native windows
Components 21
App runtime
- App lifecycle
runtime/app.js - Public API
runtime/index.js - Validation
runtime/validation.js - Launch routing
runtime/launch-routing.js - Backend plugins
runtime/app.js
Bridge and security
- Frontend bridge
runtime/bridge.js - IPC protocol
runtime/ipc.js
Native desktop host
- Native addon loader
runtime/native.js - Native runtime
src-nodeview/src/app.cpp - Native windows
src-nodeview/src/window.cpp - System WebView
src-nodeview/src/webview.cpp
Desktop capabilities
- App data
runtime/data-directory.js - Menus and shortcuts
runtime/menu.js - HTTP client
runtime/net.js - Signed updates
runtime/updater.js - Native helpers
runtime/index.js - Native packaging
src-nodeview/src/launcher.cpp
Other components
- App developer
- Web page
- Operating system
- HTTPS update host
Connections 24
- App developer → App lifecycle: creates app
README.md - Web page → Frontend bridge: invokes commands
README.md - Frontend bridge → IPC protocol: sends requests
README.md - IPC protocol → App lifecycle: dispatches commands
README.md - App lifecycle → IPC protocol: registers handlers
runtime/app.js - App lifecycle → Validation: validates options
runtime/app.js - App lifecycle → Launch routing: resolves launch config
runtime/app.js - App lifecycle → Backend plugins: starts plugins
runtime/app.js - Public API → App lifecycle: exports runtime
runtime/index.js - Public API → Native helpers: exports helpers
runtime/index.js - App lifecycle → Native addon loader: uses native host
runtime/app.js - Native addon loader → Native runtime: loads addon
- Native runtime → Native windows: creates windows
src-nodeview/src/app.cpp - Native windows → System WebView: hosts page
- System WebView → IPC protocol: exchanges messages
src-nodeview/src/webview.cpp - App lifecycle → App data: uses app data
runtime/app.js - App lifecycle → Menus and shortcuts: handles menu events
runtime/app.js - Public API → HTTP client: exports client
runtime/index.js - Public API → Signed updates: exports updater
runtime/index.js - HTTP client → HTTPS update host: fetches allowlisted URLs
README.md - Signed updates → HTTPS update host: downloads signed updates
README.md - App lifecycle → Native packaging: runs when packaged
- Native windows → Operating system: uses system WebView
README.md - Native helpers → Operating system: accesses desktop services
README.md